Skip to content
worldfires
KZ · Kazakhstan · →

Khobdinskiy fire, 25 July 2017 Khobdinskiy, Chingirlauskiy

Out · last detection 29 Jul 2017, 08:58 UTC

The fire started on 25 July 2017 in Khobdinskiy, Kazakhstan, and satellites saw it burning for 5 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 9,038 hectares from heat detections, spread across 2 municipalities.

It is the 8th largest in Aktobe Region since 2016 (of 101 with a page). Number 50 in Kazakhstan in 2017, of 239.

Burnt area
9,038ha
GWIS perimeter (Copernicus)
Duration
5days
25 Jul 2017 – 29 Jul 2017
Municipalities hit
2
districts
Started on
25 Jul
2017
Heat detections
361
in a single hotspot: 86 MW
Danger at start
34
High · FWI index
Energy released
3.1GW
sum of detected power

Where it burned

29 Jul 2017
HOTSPOTS BY DAY 25 Jul29 Jul

How it evolved, day by day

2526272829

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
37km/h · peak gust
24%lowest humidity

It had gone 0 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. Khobdinskiy where it started
    8,771 ha reached on 25 Jul
    0.6 %
  2. 293 ha reached on 29 Jul
    0.0 %

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)
25 Jul 27.1 °C 26 % 37 km/h 0.0 mm High 34
26 Jul 28.0 °C 27 % 31 km/h 0.0 mm High 34
27 Jul 29.4 °C 32 % 36 km/h 0.0 mm High 36
28 Jul 32.2 °C 28 % 19 km/h 0.0 mm High 30
29 Jul 35.5 °C 24 % 18 km/h 0.0 mm High 35
30 Jul after 37.6 °C 17 % 32 km/h 0.0 mm Very high 46
31 Jul after 30.6 °C 36 % 48 km/h 0.0 mm Very high 39
1 Aug after 29.5 °C 33 % 42 km/h 0.5 mm Very high 42
2 Aug after 29.9 °C 35 % 53 km/h 0.2 mm Extreme 50
3 Aug after 29.7 °C 26 % 40 km/h 0.0 mm Very high 42
4 Aug after 34.3 °C 22 % 38 km/h 0.0 mm Very high 46
5 Aug after 36.5 °C 19 % 42 km/h 0.0 mm Extreme 54
6 Aug after 34.3 °C 24 % 33 km/h 0.0 mm Very high 47
7 Aug after 33.4 °C 22 % 28 km/h 0.0 mm Very high 46
8 Aug after 41.3 °C 10 % 35 km/h 0.0 mm Extreme 64

Before and after, from space

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

Before · 18 Jul 2017
After · 5 Aug 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 · 361Every 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 Kazakhstan ›

Frequently asked questions

How long did the Khobdinskiy fire last?
GWIS (Copernicus) dates it between 25 July 2017 and 29 July 2017: 5 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 9,038 hectares (90.4 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Khobdinskiy (8,771 ha, 0.6 %); Chingirlauskiy (293 ha, 0.0 %).
What was the weather like?
During the fire the temperature reached 35.5 °C, humidity dropped to 24 % and gusts hit 37 km/h. The fire danger index (FWI) reached 36, class High.
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.