Skip to content
worldfires
KZ · Kazakhstan · →

Temirskiy fire, 1 August 2017 Temirskiy

Out · last detection 4 Aug 2017, 10:26 UTC

The fire started on 1 August 2017 in Temirskiy, Kazakhstan, and satellites saw it burning for 4 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 5,343 hectares from heat detections, spread across a single municipality.

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

Burnt area
5,343ha
GWIS perimeter (Copernicus)
Duration
4days
1 Aug 2017 – 4 Aug 2017
Municipalities hit
1
districts
Started on
1 Aug
2017
Heat detections
226
in a single hotspot: 260 MW
Danger at start
40
Very high · FWI index
Energy released
4.1GW
sum of detected power

Where it burned

4 Aug 2017
HOTSPOTS BY DAY 1 Aug4 Aug

How it evolved, day by day

1234

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

The weather it burned in

35°high
51km/h · peak gust
16%lowest humidity

It had gone 11 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. Temirskiy where it started
    5,342 ha reached on 1 Aug
    0.4 %

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)
1 Aug 32.9 °C 24 % 46 km/h 1.4 mm Very high 40
2 Aug 31.8 °C 37 % 51 km/h 0.2 mm Very high 48
3 Aug 31.0 °C 23 % 45 km/h 0.0 mm Very high 47
4 Aug 35.4 °C 16 % 27 km/h 0.0 mm Very high 44
5 Aug after 38.0 °C 13 % 38 km/h 0.0 mm Extreme 61
6 Aug after 38.7 °C 14 % 43 km/h 0.0 mm Extreme 63
7 Aug after 37.5 °C 20 % 37 km/h 0.0 mm Extreme 58
8 Aug after 42.7 °C 8 % 34 km/h 0.0 mm Extreme 68
9 Aug after 32.7 °C 19 % 47 km/h 0.0 mm Extreme 64
10 Aug after 27.6 °C 17 % 53 km/h 0.0 mm Extreme 68
11 Aug after 26.0 °C 18 % 46 km/h 0.0 mm Extreme 58
12 Aug after 28.1 °C 22 % 29 km/h 0.0 mm Very high 45
13 Aug after 29.6 °C 27 % 35 km/h 0.0 mm Very high 45
14 Aug after 28.4 °C 27 % 41 km/h 0.0 mm Very high 47

Before and after, from space

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

Before · 25 Jul 2017
After · 11 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 · 226Every 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 Temirskiy fire last?
GWIS (Copernicus) dates it between 1 August 2017 and 4 August 2017: 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 5,343 hectares (53.4 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Temirskiy (5,342 ha, 0.4 %).
What was the weather like?
During the fire the temperature reached 35.4 °C, humidity dropped to 16 % and gusts hit 51 km/h. The fire danger index (FWI) reached 48, class Very 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.