Skip to content
worldfires
KZ · Kazakhstan · →

Khobdinskiy fire, 22 August 2017 Khobdinskiy, Chingirlauskiy

Out · last detection 24 Aug 2017, 21:24 UTC

The fire started on 22 August 2017 in Khobdinskiy, Kazakhstan, and satellites saw it burning for 3 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 18,294 hectares from heat detections, spread across 2 municipalities.

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

Burnt area
18,294ha
GWIS perimeter (Copernicus)
Duration
3days
22 Aug 2017 – 24 Aug 2017
Municipalities hit
2
districts
Started on
22 Aug
2017
Heat detections
743
in a single hotspot: 216 MW
Danger at start
56
Extreme · FWI index
Energy released
8.5GW
sum of detected power

Where it burned

24 Aug 2017
HOTSPOTS BY DAY 22 Aug24 Aug

How it evolved, day by day

222324

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

It had gone 28 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
    12,601 ha reached on 22 Aug
    0.9 %
  2. Chingirlauskiy
    5,578 ha reached on 22 Aug
    0.8 %

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)
22 Aug 32.3 °C 15 % 43 km/h 0.0 mm Extreme 56
23 Aug 33.9 °C 10 % 41 km/h 0.0 mm Extreme 63
24 Aug 34.2 °C 13 % 37 km/h 0.0 mm Extreme 59
25 Aug after 34.7 °C 13 % 42 km/h 0.0 mm Extreme 61
26 Aug after 30.0 °C 25 % 32 km/h 0.2 mm Very high 46
27 Aug after 28.1 °C 22 % 42 km/h 0.0 mm Extreme 53
28 Aug after 29.0 °C 22 % 31 km/h 0.0 mm Very high 44
29 Aug after 32.7 °C 15 % 35 km/h 0.0 mm Very high 50
30 Aug after 36.1 °C 12 % 53 km/h 0.5 mm Very extreme 74
31 Aug after 33.4 °C 17 % 36 km/h 0.0 mm Extreme 56
1 Sept after 34.5 °C 21 % 29 km/h 0.0 mm Extreme 54
2 Sept after 39.1 °C 8 % 31 km/h 0.0 mm Extreme 61
3 Sept after 32.5 °C 16 % 32 km/h 0.0 mm Extreme 57

Before and after, from space

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

Before · 15 Aug 2017
After · 31 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 · 743Every 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 22 August 2017 and 24 August 2017: 3 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 18,294 hectares (182.9 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Khobdinskiy (12,601 ha, 0.9 %); Chingirlauskiy (5,578 ha, 0.8 %).
What was the weather like?
During the fire the temperature reached 34.2 °C, humidity dropped to 10 % and gusts hit 43 km/h. The fire danger index (FWI) reached 63, 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.