Skip to content
worldfires
RU · Russia · –

Kuvandyksky District fire, 1 September 2022 Kuvandyksky District, городской округ Медногорск

Out · last detection 4 Sept 2022, 08:28 UTC

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

It is the 3th largest in Orenburg Oblast since 2016 (of 16 with a page). Number 87 in Russia in 2022, of 400.

Burnt area
10,193ha
GWIS perimeter (Copernicus)
Duration
4days
1 Sept 2022 – 4 Sept 2022
Municipalities hit
2
districts
Started on
1 Sept
2022
Heat detections
540
in a single hotspot: 265 MW
Danger at start
59
Extreme · FWI index
Average daily power
2.1GW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 1 Sept4 Sept
4 Sept 2022

How it evolved, day by day

1 Sept 2022 · 6,856 MW · 348 2 Sept 2022 · 1,317 MW · 145 3 Sept 2022 · 263 MW · 45 4 Sept 2022 · 12 MW · 2
1 Sept 2 Sept 3 Sept 4 Sept

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

The weather it burned in

34°high
46km/h · peak gust
14%lowest humidity

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

This area had burned before

44% of the perimeter overlaps earlier fires recorded since 2016: 4,522 ha in 2018.

How big is it?

10 km
It burned the equivalent of 6.4% of the area of London (102 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. Kuvandyksky District where it started
    7,173 ha reached on 1 Sept
    1.2 %
  2. 2,979 ha reached on 1 Sept
    8.5 %

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 area0.22 ha
Residents< 20

Inside the perimeter there were about 0.22 hectares of 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)

Started with Extreme FWI: < 1 % of the area in Russia Very dry air: 6.1 % of the area in Russia

Day High Min. humidity Peak gust Rain Danger (FWI)
1 Sept 34.3 °C 14 % 42 km/h 0.0 mm Extreme 59
2 Sept 34.0 °C 17 % 46 km/h 0.0 mm Very extreme 72
3 Sept 25.7 °C 16 % 44 km/h 0.0 mm Very high 45
4 Sept 25.9 °C 23 % 40 km/h 0.0 mm High 34
5 Sept after 24.5 °C 28 % 39 km/h 0.3 mm Very high 41
6 Sept after 12.7 °C 56 % 43 km/h 0.0 mm High 23
7 Sept after 15.6 °C 36 % 45 km/h 0.5 mm High 30
8 Sept after 16.8 °C 33 % 46 km/h 0.0 mm High 35
9 Sept after 18.3 °C 28 % 44 km/h 0.5 mm High 35
10 Sept after 10.0 °C 81 % 42 km/h 7.5 mm Very low 1

Its twins: fires that started in the same weather

It started with an FWI of 59.1, a minimum humidity of 14% and 29 days without rain. Fires in the area that started in weather like this since 2017: 11.

FWI at the start 59.1
Minimum humidity 14 %
Days without rain 29
this fire chosen twins rest of the area
Almost identicalSimilar

Outlines of the closest twins

Mugalzharskiy fire, September 2017
3,554 ha 2 days FWI 56.0 Min. humidity 13 % 182 km away, in 2017

First rain (1 mm or more) after it ended: 7.8 mm on 8 Sept.

What happened to them

Fires in the area that started in similar weather: 11. With fewer than 15 we give no figures: they would be more noise than signal.

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

7.5 mmfirst rain
10 Sept6 days after it ended
46km/h · max. gust

It was considered over on 4 Sept, and on 10 Sept 7.5 mm fell. We do not know whether the rain or the firefighters put it out.

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 · 25 Aug 2022
After · 11 Sept 2022

If the day is cloudy, change the date: each satellite passes once a day. In false colour the burnt ground looks brown or red.

The smoke

CAMS · Copernicus

On 3 September 2022 the air beside the fire reached 37 µg/m³ of PM2.5, but no daily average passed the WHO guideline (15).

PM2.5 peak37 µg/m³
Days over the guideline0 days
PM1053 µg/m³
Optical depth0.56
30 Aug1 Sept3 Sept5 Sept7 Sept
Good Fair Moderate Poor Very poor Extremely poor

Particles from the Copernicus CAMS model at the centre of the perimeter; these are not measurements in each town. The pale bar is the worst hour, the solid one the daily average.

Open-Meteo.com (CC BY 4.0) · Copernicus Atmosphere Monitoring Service (CAMS)

Detections table · 540Every 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 Kuvandyksky District fire last?
GWIS (Copernicus) dates it between 1 September 2022 and 4 September 2022: 4 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 10,193 hectares (101.9 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Kuvandyksky District (7,173 ha, 1.2 %); городской округ Медногорск (2,979 ha, 8.5 %).
What was the weather like?
During the fire the temperature reached 34.3 °C, humidity dropped to 14 % and gusts hit 46 km/h. The fire danger index (FWI) reached 72, class Very extreme.
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 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. 540 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.