Burned area
satellite only8,828ha
Perimeter published by GWIS (Copernicus).
- Source
- GWIS (Copernicus)
- Date
- 1 Jul 2017 – 7 Jul 2017
+− cross-check
No official record is matched to this page to compare it with.
RU · Russia · –
Tungiro-Olyokminsky District fire, 1 July 2017 Tungiro-Olyokminsky District
Out · last detection 7 Jul 2017, 17:59 UTC
The fire started on 1 July 2017 in Tungiro-Olyokminsky District, Russia, and satellites saw it burning for 7 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 8,828 hectares from heat detections, spread across a single municipality.
It is the 136th largest in Zabaykalsky Krai since 2016 (of 465 with a page). Number 83 in Russia in 2017, of 367.
Use this data
Fire page data · version 2026-10-24matches the official recordwith caveatssatellite onlymodel
When copying, the sentence is
Tick the figures you want: they make up the lede and the CSV.
Duration by satellite
satellite only7days
1 Jul 2017 to 7 Jul 2017: first and last day with fire on the page.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- last detection: 7 Jul 2017, 17:59 UTC
+− cross-check
Satellites pass a few times a day and cloud or smoke can hide the fire: a lack of detections is not an official extinction. Each country’s emergency service declares a fire contained or out.
Start
satellite only1 Jul 2017
First day with fire seen by the satellites or the perimeter.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 1 Jul 2017
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Hotspots
satellite only578
VIIRS detections at 375 m. Most intense hotspot: 250 MW.
- Source
- NASA FIRMS · VIIRS (Suomi NPP)
- Date
- 1 Jul 2017 – 7 Jul 2017
+− cross-check
There is no official record to compare with. Each hotspot is a pixel detected in one satellite pass, not a separate fire.
The worst day
satellite only4,477MW
Total radiative power on 3 July 2017; hotspots that day: 219.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 3 Jul 2017
+− cross-check
Fire radiative power (FRP) measures the energy the fire gives off when the satellite passes. Added up by day, it compares intensity, not area.
Danger at the start
model7.4FWI · low
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 1.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 1 Jul 2017, local noon
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
This is an index computed from weather model data, not a measurement of the fire nor an official warning. Danger warnings are issued by each country’s authority. Emergency number and official warnings
Weather during the fire
model32.8°C · 35% RH
High of 32.8 °C and minimum humidity of 35% on 4 July 2017; gusts of 43 km/h on 6 July 2017.
- Source
- weather model at the fire’s grid cell
- Date
- 1 Jul 2017 – 7 Jul 2017
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
These are model values for a cell of about 25 km, not from a weather station: they may differ from what was measured on the ground.
This page’s change log has been kept since 24 October 2026: every night what it publishes is compared and the difference is logged. Anything earlier is reconstructed from each source’s date and marked as reconstructed.
Show
-
· reconstructed GHSLPopulation and built-up area computed
-
· reconstructed weatherWeather and FWI computed from the ERA5 reanalysis
What was saved on 24 October 2026
Every night a snapshot of what the page shows is saved. If anything changes, it appears in the list as a log entry.
- Area
- 8,828 ha
- Dates
- 1 Jul 2017 – 7 Jul 2017
- Name
- Tungiro-Olyokminsky District
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/tungiro-olyokminsky-district-2017-07?v=2026-10-24A version keeps the area, dates, name and official record; the area as it was logged (changes under 2% are not logged). The map, hotspots and weather always show today’s data.
Citation
A lede of about 60 words figures only, no adjectives
CSV for this fire tungiro-olyokminsky-district-2017-07.csv · daily, no individual hotspots
| fecha | focos_viirs | frp_mw | tmax_c | tmin_c | hr_min_pct | viento_max_kmh | racha_max_kmh | precip_mm | fwi | clase_fwi | dentro_del_incendio |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2017-07-01 | 4 | 27 | 30.2 | 12 | 30 | 8.9 | 15.5 | 0 | 7.4 | bajo | 1 |
| 2017-07-02 | 117 | 1,583 | 32.1 | 11.5 | 26 | 12.5 | 28.4 | 0 | 14.3 | moderado | 1 |
| 2017-07-03 | 219 | 4,477 | 31.9 | 13.3 | 32 | 15.8 | 38.9 | 0 | 17.1 | moderado | 1 |
| 2017-07-04 | 38 | 946 | 32.8 | 14.5 | 35 | 15.9 | 41.8 | 0.1 | 18.3 | moderado | 1 |
| 2017-07-05 | 53 | 520 | 28.6 | 18.3 | 52 | 14.1 | 38.5 | 2.6 | 3.5 | muy_bajo | 1 |
| 2017-07-06 | 84 | 477 | 26.8 | 15.1 | 37 | 15.5 | 42.8 | 1.1 | 8.1 | bajo | 1 |
| 2017-07-07 | 63 | 148 | 28.1 | 10 | 37 | 8.2 | 18 | 0 | 10.9 | bajo | 1 |
| 2017-07-08 | 0 | 0 | 29.1 | 15.4 | 45 | 11.7 | 31.7 | 0 | 12.7 | moderado | 0 |
| 2017-07-09 | 0 | 0 | 27.1 | 18.1 | 57 | 12.2 | 45 | 8.8 | 0.8 | muy_bajo | 0 |
It is generated in your browser from this page’s data: one file per fire, aggregated by day and without individual hotspots.
Live widget for your story
It updates itself while the fire is still active and links to this page. Free, with the attribution shown at the bottom.
Sources for this page: GWIS (Copernicus), NASA FIRMS (VIIRS), ERA5 (ECMWF/Copernicus C3S) · Open-Meteo.com (CC BY 4.0), GHSL (JRC). Open-Meteo.com · How we build fire pages: methodology
- Burnt area
- 8,828ha
- GWIS perimeter (Copernicus)
- Duration
- 7days
- 1 Jul 2017 – 7 Jul 2017
- Municipalities hit
- 1
- districts
- Started on
- 1 Jul
- 2017
- Heat detections
- 578
- in a single hotspot: 250 MW
- Danger at start
- 7
- Low · FWI index
- Average daily power
- 1.2GW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
1 Jul7 Jul
7 Jul 2017
How it evolved, day by day
1 Jul
3 Jul
5 Jul
7 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
33°high
43km/h · peak gust
26%lowest humidity
It had gone one day without rain (1 mm or more) when it started. Rain came after the fire: 8.8 mm on 9 Jul.
This area had burned before
No earlier perimeters overlap this fire since 2016, when the satellite record begins.
How big is it?
London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).
Moscow boundary: geoBoundaries · OpenStreetMap, Wambacher · © OpenStreetMap contributors (ODbL 1.0).
Paris boundary: geoBoundaries · Institut national de l'information géographique et forestière (IGN-F) (Etalab Open License 2.0).
Madrid boundary: geoBoundaries · Open Data ESRI, IGN Central Registry of Cartography Area (CC BY 4.0).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each town
-
Tungiro-Olyokminsky District where it started8,832 ha reached on 1 Jul0.2 %
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 2015Built-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) |
|---|---|---|---|---|---|
| 1 Jul | 30.2 °C | 30 % | 16 km/h | 0.0 mm | Low 7 |
| 2 Jul | 32.1 °C | 26 % | 28 km/h | 0.0 mm | Moderate 14 |
| 3 Jul | 31.9 °C | 32 % | 39 km/h | 0.0 mm | Moderate 17 |
| 4 Jul | 32.8 °C | 35 % | 42 km/h | 0.1 mm | Moderate 18 |
| 5 Jul | 28.6 °C | 52 % | 38 km/h | 2.6 mm | Very low 4 |
| 6 Jul | 26.8 °C | 37 % | 43 km/h | 1.1 mm | Low 8 |
| 7 Jul | 28.1 °C | 37 % | 18 km/h | 0.0 mm | Low 11 |
| 8 Jul after | 29.1 °C | 45 % | 32 km/h | 0.0 mm | Moderate 13 |
| 9 Jul after | 27.1 °C | 57 % | 45 km/h | 8.8 mm | Very low 1 |
Its twins: fires that started in the same weather
It started with an FWI of 7.4, a minimum humidity of 30% and 1 day without rain. Fires in the area that started in weather like this since 2016: 16.
FWI at the start
7.4
Minimum humidity
30 %
Days without rain
1
this fire
chosen twins
rest of the area
Almost identicalSimilar
Outlines of the closest twins
This fire · Tungiro-Olyokminsky District fire, 1 July 2017
8,828 ha
7 days
FWI 7.4
Min. humidity 30 %
Tyndinsky District fire, June 2019
11,958 ha
23 days
FWI 7.2
Min. humidity 30 %
119 km away, in 2019
First rain (1 mm or more) after it ended: 7.0 mm on 9 Jul.
Mogochinsky District fire, July 2024
5,974 ha
13 days
FWI 7.8
Min. humidity 30 %
160 km away, in 2024
First rain (1 mm or more) after it ended: 7.4 mm on 4 Aug.
Tungiro-Olyokminsky District fire, May 2024
18,406 ha
19 days
FWI 10.9
Min. humidity 30 %
73 km away, in 2024
First rain (1 mm or more) after it ended: 3.4 mm on 16 Jun.
Tyndinsky District fire, May 2024
3,115 ha
14 days
FWI 6.8
Min. humidity 30 %
190 km away, in 2024
First rain (1 mm or more) after it ended: 1.1 mm on 9 Jun.
Mogochinsky District fire, June 2024
8,675 ha
20 days
FWI 5.0
Min. humidity 30 %
112 km away, in 2024
First rain (1 mm or more) after it ended: 1.7 mm on 13 Jul.
What happened to them
- 14 days
- median duration
- 5,326 ha
- median area
- 25 %
- went past 10,000 ha
- 4.6 mm
- rain at the end (median; 15 of 16 had it)
It was 1.7 times larger than the median of its twins and lasted 7 days, against 14 days.
Only 4 of its 16 twins burned more. The weather on the first day does not explain everything: the wind in the following days, the fuel and the firefighting also count. In 1 of 16, 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 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
8.8 mmfirst rain
9 Jul2 days after it ended
43km/h · max. gust
It was considered over on 7 Jul, and on 9 Jul 8.8 mm fell. We do not know whether the rain or the firefighters put it out. Twins with rain when they ended: 15 of 16, 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 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.
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
↔
Before · 24 Jun 2017
After · 14 Jul 2017
Sentinel-2 did not pass over on that day. Try another date, or use false colour, which is daily.
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 · 578Every 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 time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 11,791 haTungiro-Olyokminsky District22 June 2024 · 21 days · 9 km away
- 8,610 haTungiro-Olyokminsky District22 June 2024 · 20 days · 19 km away
- 14,793 haTungiro-Olyokminsky District17 June 2019 · 27 days · 30 km away
- 6,892 haTungiro-Olyokminsky District24 June 2024 · 17 days · 32 km away
- 6,376 haTungiro-Olyokminsky District3 June 2024 · 7 days · 38 km away
- 3,188 haTungiro-Olyokminsky District6 July 2019 · 9 days · 39 km away
Frequently asked questions
- How long did the Tungiro-Olyokminsky District fire last?
- GWIS (Copernicus) dates it between 1 July 2017 and 7 July 2017: 7 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,828 hectares (88.3 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Tungiro-Olyokminsky District (8,832 ha, 0.2 %).
- What was the weather like?
- During the fire the temperature reached 32.8 °C, humidity dropped to 26 % and gusts hit 43 km/h. The fire danger index (FWI) reached 18, 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 2016 with a similar FWI, humidity and dry spell: 16. Their median duration was 14 days and their median area 5,326 ha; 25 % went past 10,000 ha. Only 4 of its 16 twins burned more. The weather on the first day does not explain everything: the wind in the following days, the fuel and the firefighting also count. In 1 of 16, 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 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.
No changes since 24 October 2026.
RSS Changes to this page With cross-checks and a citable version
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
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. 578 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.
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.