Skip to content
worldfires
KZ · Kazakhstan · →

Urdinskiy fire, July 2017 Urdinskiy

Out · last detection 6 Jul 2017, 09:29 UTC

The fire started on 6 July 2017 in Urdinskiy, Kazakhstan, and satellites saw it burning for 1 day. Copernicus’s global GWIS system rebuilt a burnt perimeter of 3,624 hectares from heat detections, spread across a single municipality.

It is the 44th largest in West Kazakhstan Region since 2016 (of 59 with a page). Number 181 in Kazakhstan in 2017, of 239.

Burnt area
3,624ha
GWIS perimeter (Copernicus)
Duration
1day
6 Jul 2017 – 6 Jul 2017
Municipalities hit
1
districts
Started on
6 Jul
2017
Heat detections
122
in a single hotspot: 144 MW
Danger at start
56
Extreme · FWI index
Energy released
3.4GW
sum of detected power

Where it burned

HOTSPOTS BY DAY 6 Jul6 Jul

How it evolved, day by day

6

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

The weather it burned in

26°high
55km/h · peak gust
24%lowest humidity

It had gone 13 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.

What happened to each town

  1. Urdinskiy where it started
    3,654 ha reached on 6 Jul
    0.2 %

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)
6 Jul 26.4 °C 24 % 55 km/h 0.0 mm Extreme 56
7 Jul after 28.8 °C 20 % 27 km/h 0.0 mm Very high 39
8 Jul after 25.3 °C 21 % 48 km/h 0.5 mm Extreme 53
9 Jul after 26.0 °C 20 % 51 km/h 0.0 mm Extreme 56
10 Jul after 25.4 °C 26 % 33 km/h 0.0 mm Very high 41
11 Jul after 25.7 °C 30 % 55 km/h 0.4 mm Extreme 58
12 Jul after 26.9 °C 28 % 44 km/h 0.0 mm Very high 46
13 Jul after 29.7 °C 22 % 25 km/h 0.0 mm High 36
14 Jul after 31.3 °C 20 % 30 km/h 0.0 mm Very high 41
15 Jul after 33.0 °C 15 % 39 km/h 0.0 mm Extreme 56
16 Jul after 34.5 °C 14 % 29 km/h 0.0 mm Very high 49

Before and after, from space

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

Before · 29 Jun 2017
After · 13 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 · 122Every 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

Frequently asked questions

How long did the Urdinskiy fire last?
GWIS (Copernicus) dates it between 6 July 2017 and 6 July 2017: 1 day 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,624 hectares (36.2 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Urdinskiy (3,654 ha, 0.2 %).
What was the weather like?
During the fire the temperature reached 26.4 °C, humidity dropped to 24 % and gusts hit 55 km/h. The fire danger index (FWI) reached 56, class Extreme.
Where does this data come from?
From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Kazakhstan (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.