Skip to content
worldfires
KZ · Kazakhstan · →

Taskalinskiy fire, October 2019 Taskalinskiy, Zelenovskiy

Out · last detection 7 Oct 2019, 08:59 UTC

The fire started on 6 October 2019 in Taskalinskiy, Kazakhstan, and satellites saw it burning for 2 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 3,261 hectares from heat detections, spread across 2 municipalities.

It is the 55th largest in West Kazakhstan Region since 2016 (of 59 with a page). Number 137 in Kazakhstan in 2019, of 163.

Burnt area
3,261ha
GWIS perimeter (Copernicus)
Duration
2days
6 Oct 2019 – 7 Oct 2019
Municipalities hit
2
districts
Started on
6 Oct
2019
Heat detections
148
in a single hotspot: 356 MW
Danger at start
38
Very high · FWI index
Energy released
4.7GW
sum of detected power

Where it burned

7 Oct 2019
HOTSPOTS BY DAY 6 Oct7 Oct

How it evolved, day by day

67

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

The weather it burned in

23°high
54km/h · peak gust
8%lowest humidity

It had gone 12 days without rain (1 mm or more) when it started. Rain came after the fire: 10.4 mm on 12 Oct.

This area had burned before

18% of the perimeter overlaps earlier fires recorded since 2016: 603 ha in 2017.

What happened to each town

  1. Taskalinskiy where it started
    2,612 ha reached on 6 Oct
    0.3 %
  2. 651 ha reached on 6 Oct
    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)
6 Oct 22.8 °C 8 % 44 km/h 0.0 mm Very high 38
7 Oct 21.4 °C 17 % 54 km/h 0.8 mm High 34
8 Oct after 10.4 °C 49 % 42 km/h 0.0 mm Moderate 20
9 Oct after 9.4 °C 68 % 37 km/h 0.6 mm Moderate 11
10 Oct after 13.2 °C 50 % 31 km/h 0.0 mm Moderate 12
11 Oct after 15.6 °C 51 % 49 km/h 0.0 mm Moderate 16
12 Oct after 12.1 °C 51 % 27 km/h 10.4 mm Very low 0

Before and after, from space

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

Before · 29 Sept 2019
After · 14 Oct 2019

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 · 148Every 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 Taskalinskiy fire last?
GWIS (Copernicus) dates it between 6 October 2019 and 7 October 2019: 2 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 3,261 hectares (32.6 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Taskalinskiy (2,612 ha, 0.3 %); Zelenovskiy (651 ha, 0.1 %).
What was the weather like?
During the fire the temperature reached 22.8 °C, humidity dropped to 8 % and gusts hit 54 km/h. The fire danger index (FWI) reached 38, 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.