Skip to content
worldfires
RU · Russia · –

Zeysky District fire, 30 June 2017 Zeysky District

Out · last detection 9 Jul 2017, 17:21 UTC

The fire started on 30 June 2017 in Zeysky District, Russia, and satellites saw it burning for 10 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 8,001 hectares from heat detections, spread across a single municipality.

It is the 184th largest in Amur Oblast since 2016 (of 491 with a page). Number 97 in Russia in 2017, of 367.

Burnt area
8,001ha
GWIS perimeter (Copernicus)
Duration
10days
30 Jun 2017 – 9 Jul 2017
Municipalities hit
1
districts
Started on
30 Jun
2017
Heat detections
1,023
in a single hotspot: 98 MW
Danger at start
15
Moderate · FWI index
Average daily power
758MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 30 Jun9 Jul
9 Jul 2017

How it evolved, day by day

30 Jun 2017 · 16 MW · 6 1 Jul 2017 · 160 MW · 28 2 Jul 2017 · 375 MW · 63 3 Jul 2017 · 354 MW · 67 4 Jul 2017 · 1,204 MW · 145 5 Jul 2017 · 1,051 MW · 82 6 Jul 2017 · 2,078 MW · 207 7 Jul 2017 · 1,094 MW · 176 8 Jul 2017 · 832 MW · 160 9 Jul 2017 · 418 MW · 89
30 Jun 2 Jul 4 Jul 6 Jul 8 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

36°high
53km/h · peak gust
21%lowest humidity

It had gone 11 days without rain (1 mm or more) when it started. Rain came after the fire: 8.7 mm on 10 Jul.

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 5.1% of the area of London (80 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. Zeysky District where it started
    8,135 ha reached on 30 Jun
    0.1 %

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 area0.84 ha
Residents≈ 30

Inside the perimeter there were about 0.84 hectares of built-up land and about 30 residents (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)
30 Jun 29.3 °C 35 % 35 km/h 0.9 mm Moderate 15
1 Jul 32.4 °C 25 % 20 km/h 0.0 mm High 22
2 Jul 34.1 °C 21 % 30 km/h 0.0 mm High 27
3 Jul 33.9 °C 21 % 31 km/h 0.0 mm High 28
4 Jul 34.9 °C 22 % 37 km/h 0.0 mm High 31
5 Jul 36.3 °C 25 % 34 km/h 0.0 mm High 31
6 Jul 34.9 °C 28 % 53 km/h 0.2 mm High 38
7 Jul 32.0 °C 24 % 33 km/h 0.0 mm High 32
8 Jul 33.0 °C 23 % 24 km/h 0.0 mm High 33
9 Jul 28.0 °C 40 % 46 km/h 0.2 mm High 30
10 Jul after 21.9 °C 56 % 52 km/h 8.7 mm Very low 3

Its twins: fires that started in the same weather

It started with an FWI of 14.8, a minimum humidity of 35% and 11 days without rain. Fires in the area that started in weather like this since 2016: 45.

FWI at the start 14.8
Minimum humidity 35 %
Days without rain 11
this fire chosen twins rest of the area
Almost identicalSimilar

Outlines of the closest twins

Zeysky District fire, July 2024
7,659 ha 12 days FWI 15.4 Min. humidity 35 % 68 km away, in 2024

First rain (1 mm or more) after it ended: 9.7 mm on 14 Jul.

What happened to them

14 days
median duration
8,798 ha
median area
44 %
went past 10,000 ha
9.7 mm
rain at the end (median; 44 of 45 had it)

It burned an area similar to its twins (8,001 ha against a median of 8,798 ha) and lasted 10 days, against 14 days.

In 1 of 45, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 9.7 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

8.7 mmfirst rain
10 Julthe day after it ended
53km/h · max. gust

It was considered over on 9 Jul, and on 10 Jul 8.7 mm fell. We do not know whether the rain or the firefighters put it out. Twins with rain when they ended: 44 of 45, with a median of 9.7 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 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 · 23 Jun 2017
After · 16 Jul 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 · 1,023Every 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 Zeysky District fire last?
GWIS (Copernicus) dates it between 30 June 2017 and 9 July 2017: 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 8,001 hectares (80.0 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Zeysky District (8,135 ha, 0.1 %).
What was the weather like?
During the fire the temperature reached 36.3 °C, humidity dropped to 21 % and gusts hit 53 km/h. The fire danger index (FWI) reached 38, 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.
How did the fires that started in similar weather in this area end?
Fires less than 250 km away that started since 2016 with a similar FWI, humidity and dry spell: 45. Their median duration was 14 days and their median area 8,798 ha; 44 % went past 10,000 ha. In 1 of 45, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 9.7 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. 1,023 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.