Skip to content
worldfires
en
RU · Russia · →

Tigilsky District fire, May 2016 Tigilsky District

Out · last detection 27 Jun 2016, 01:19 UTC

The fire started on 26 May 2016 in Tigilsky District, Russia, and satellites saw it burning for 33 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 191,474 hectares from heat detections, spread across a single municipality.

This page is probably a fire complex, not a single fire. GWIS merges into one perimeter the fires that touch over weeks, which in large burning seasons can join dozens of separate fires. The total area is reliable; the origin and dates refer to the whole complex.

Other fire pages in the same area and on the same dates:

It is the largest fire in Kamchatka Krai since 2016 (of 63 with a page). The largest in Russia in 2016, of 692.

Compare with…

Suggestions: Tigilsky District · 2016Tigilsky District · 2016

Burnt area
191,474ha
GWIS perimeter (Copernicus)
Duration
33days
26 May 2016 – 27 Jun 2016
Municipalities hit
1
districts
Started on
26 May
2016
Heat detections
13,859
in a single hotspot: 580 MW
Danger at start
4
Very low · FWI index
Average daily power
9.5GW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 26 May27 Jun
27 Jun 2016

How it evolved, day by day

26 May 2016 · 264 MW · 60 27 May 2016 · 777 MW · 48 28 May 2016 · 13,960 MW · 406 29 May 2016 · 13,028 MW · 563 30 May 2016 · 69 MW · 24 31 May 2016 · 6,362 MW · 542 1 Jun 2016 · 401 MW · 25 2 Jun 2016 · 2,643 MW · 390 3 Jun 2016 · 19,846 MW · 1288 5 Jun 2016 · 49,392 MW · 2149 6 Jun 2016 · 44,191 MW · 2291 7 Jun 2016 · 36,087 MW · 1991 8 Jun 2016 · 17,080 MW · 856 9 Jun 2016 · 16,094 MW · 768 10 Jun 2016 · 9,566 MW · 605 11 Jun 2016 · 943 MW · 58 14 Jun 2016 · 216 MW · 52 15 Jun 2016 · 1,510 MW · 143 16 Jun 2016 · 3,527 MW · 272 17 Jun 2016 · 1,424 MW · 118 20 Jun 2016 · 348 MW · 34 22 Jun 2016 · 8 MW · 4 23 Jun 2016 · 6,550 MW · 536 24 Jun 2016 · 9,722 MW · 418 25 Jun 2016 · 2,717 MW · 210 26 Jun 2016 · 33 MW · 3 27 Jun 2016 · 21 MW · 5
26 May 30 May 3 Jun 5 Jun 8 Jun 14 Jun 20 Jun 25 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

23°high
60km/h · peak gust
27%lowest humidity

It had gone 3 days without rain (1 mm or more) when it started.

This area had burned before

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

How big is it?

20 km
It burned the equivalent of 1.2 times the area of London (1,915 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. Tigilsky District where it started
    184,685 ha reached on 26 May
    2.9 %

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 2015
Built-up area< 0.1 ha
Residents< 20

Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2015, 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)
26 May 14.5 °C 44 % 27 km/h 0.0 mm Very low 4
27 May 14.6 °C 47 % 30 km/h 0.0 mm Very low 5
28 May 19.6 °C 29 % 55 km/h 0.0 mm Moderate 13
29 May 13.7 °C 42 % 52 km/h 0.0 mm Moderate 12
30 May 9.0 °C 58 % 55 km/h 0.0 mm Low 10
31 May 13.2 °C 43 % 47 km/h 0.0 mm Low 9
1 Jun 9.9 °C 61 % 34 km/h 1.2 mm Very low 2
2 Jun 14.1 °C 53 % 30 km/h 0.0 mm Very low 4
3 Jun 18.3 °C 32 % 37 km/h 0.0 mm Low 10
4 Jun 16.4 °C 38 % 46 km/h 0.0 mm Moderate 12
5 Jun 18.2 °C 27 % 60 km/h 0.0 mm Moderate 20
6 Jun 19.6 °C 30 % 49 km/h 0.0 mm Moderate 17
7 Jun 18.4 °C 31 % 52 km/h 0.0 mm Moderate 18
8 Jun 14.4 °C 55 % 35 km/h 0.0 mm Low 11
9 Jun 14.5 °C 45 % 35 km/h 0.0 mm Low 11
10 Jun 12.0 °C 59 % 30 km/h 0.0 mm Low 9
11 Jun 9.3 °C 67 % 31 km/h 0.6 mm Low 7
12 Jun 8.4 °C 68 % 29 km/h 1.3 mm Very low 3
13 Jun 11.3 °C 66 % 27 km/h 0.1 mm Very low 4
14 Jun 12.5 °C 69 % 30 km/h 0.0 mm Very low 4
15 Jun 13.0 °C 65 % 32 km/h 0.0 mm Low 6
16 Jun 11.5 °C 68 % 32 km/h 0.0 mm Low 6
17 Jun 11.7 °C 64 % 32 km/h 0.0 mm Low 6
18 Jun 10.6 °C 75 % 32 km/h 0.9 mm Very low 4
19 Jun 10.8 °C 73 % 33 km/h 0.0 mm Low 5
20 Jun 14.3 °C 65 % 36 km/h 0.0 mm Low 6
21 Jun 13.2 °C 71 % 28 km/h 0.0 mm Low 6
22 Jun 13.7 °C 75 % 37 km/h 0.0 mm Low 7
23 Jun 19.0 °C 49 % 58 km/h 0.0 mm Moderate 15
24 Jun 17.0 °C 56 % 32 km/h 0.0 mm Low 11
25 Jun 20.2 °C 45 % 34 km/h 0.0 mm Moderate 14
26 Jun 22.9 °C 43 % 27 km/h 0.0 mm Moderate 14
27 Jun 17.5 °C 66 % 31 km/h 5.2 mm Very low 1
28 Jun after 12.4 °C 77 % 29 km/h 0.0 mm Very low 2
29 Jun after 10.8 °C 83 % 26 km/h 0.1 mm Very low 2
30 Jun after 13.3 °C 76 % 19 km/h 0.7 mm Very low 2
1 Jul after 14.3 °C 71 % 30 km/h 0.0 mm Very low 3
2 Jul after 17.8 °C 61 % 38 km/h 0.0 mm Low 6
3 Jul after 16.0 °C 66 % 29 km/h 0.0 mm Low 6
4 Jul after 14.3 °C 69 % 37 km/h 0.0 mm Low 7
5 Jul after 15.5 °C 62 % 40 km/h 0.0 mm Low 9
6 Jul after 15.9 °C 62 % 37 km/h 0.0 mm Low 9
7 Jul after 16.6 °C 58 % 27 km/h 0.0 mm Low 9

Before and after, from space

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

Before · 19 May 2016
After · 4 Jul 2016

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 · 13,859Every 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 Tigilsky District fire last?
According to the heat detections seen by satellite inside the perimeter, it burned from 26 May 2016 to 27 June 2016 (33 days). The perimeter dates it from 26 May 2016 to 26 June 2016.
How much area did it burn?
The perimeter GWIS (Copernicus) rebuilt from heat detections is 191,474 hectares (1,914.7 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Tigilsky District (184,685 ha, 2.9 %).
What was the weather like?
During the fire the temperature reached 22.9 °C, humidity dropped to 27 % and gusts hit 60 km/h. The fire danger index (FWI) reached 20, 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.

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 · 1 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
  1. Last day with fire: 26 June 2016 → 27 June 2016.

RSS Changes to this page

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; 4 polygons grouped in this page.
  • Dates adjusted with the VIIRS detections inside the perimeter, which said 26 May 2016 to 26 June 2016. 13,859 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 2015, 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.