Skip to content
worldfires
KZ · Kazakhstan · →

Inderskiy fire, 30 July 2017 Inderskiy, Isatayskiy

Out · last detection 30 Jul 2017, 22:34 UTC

The fire started on 30 July 2017 in Inderskiy, Kazakhstan, and satellites saw it burning for 1 day. Copernicus’s global GWIS system rebuilt a burnt perimeter of 12,394 hectares from heat detections, spread across 2 municipalities.

It is the 5th largest in Atyrau Region since 2016 (of 43 with a page). Number 30 in Kazakhstan in 2017, of 239.

Burnt area
12,394ha
GWIS perimeter (Copernicus)
Duration
1day
30 Jul 2017 – 30 Jul 2017
Municipalities hit
2
districts
Started on
30 Jul
2017
Heat detections
371
in a single hotspot: 582 MW
Danger at start
65
Extreme · FWI index
Energy released
14.4GW
sum of detected power

Where it burned

HOTSPOTS BY DAY 30 Jul30 Jul

How it evolved, day by day

30

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

The weather it burned in

37°high
54km/h · peak gust
22%lowest humidity

It had gone 18 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. Inderskiy where it started
    10,357 ha reached on 30 Jul
    0.9 %
  2. 2,021 ha reached on 30 Jul
    0.1 %

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)
30 Jul 37.0 °C 22 % 54 km/h 0.0 mm Extreme 65
31 Jul after 34.0 °C 20 % 43 km/h 0.6 mm Extreme 55
1 Aug after 28.9 °C 36 % 45 km/h 0.0 mm Very high 47
2 Aug after 33.9 °C 24 % 45 km/h 0.0 mm Extreme 52
3 Aug after 33.8 °C 20 % 30 km/h 0.0 mm Very high 43
4 Aug after 36.5 °C 16 % 19 km/h 0.0 mm Very high 46
5 Aug after 38.4 °C 15 % 28 km/h 0.0 mm Extreme 54
6 Aug after 39.8 °C 11 % 32 km/h 0.0 mm Extreme 59
7 Aug after 40.6 °C 10 % 26 km/h 0.0 mm Extreme 59
8 Aug after 42.4 °C 7 % 27 km/h 0.0 mm Extreme 65
9 Aug after 35.1 °C 16 % 48 km/h 0.0 mm Very extreme 76

Before and after, from space

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

Before · 23 Jul 2017
After · 6 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 · 371Every 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 Inderskiy fire last?
GWIS (Copernicus) dates it between 30 July 2017 and 30 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 12,394 hectares (123.9 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Inderskiy (10,357 ha, 0.9 %); Isatayskiy (2,021 ha, 0.1 %).
What was the weather like?
During the fire the temperature reached 37.0 °C, humidity dropped to 22 % and gusts hit 54 km/h. The fire danger index (FWI) reached 65, 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.