Skip to content
worldfires
KZ · Kazakhstan · →

Dzhangil`dinskiy fire, 15 August 2016 Жангелді ауданы · Dzhangil`dinskiy, Naurzumskiy

Out · last detection 26 Aug 2016, 21:30 UTC

The fire started on 15 August 2016 in Dzhangil`dinskiy, Kazakhstan, and satellites saw it burning for 12 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 17,407 hectares from heat detections, spread across 2 municipalities.

It is the 3th largest in Kostanay Region since 2016 (of 79 with a page). The largest in Kazakhstan in 2016, of 36.

Compare with…
Burnt area
17,407ha
GWIS perimeter (Copernicus)
Duration
12days
15 Aug 2016 – 26 Aug 2016
Municipalities hit
2
districts
Started on
15 Aug
2016
Heat detections
921
in a single hotspot: 90 MW
Danger at start
43
Very high · FWI index
Average daily power
678MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 15 Aug26 Aug
26 Aug 2016

How it evolved, day by day

15 Aug 2016 · 353 MW · 28 16 Aug 2016 · 38 MW · 13 17 Aug 2016 · 36 MW · 2 18 Aug 2016 · 56 MW · 14 19 Aug 2016 · 17 MW · 12 20 Aug 2016 · 98 MW · 32 21 Aug 2016 · 25 MW · 17 22 Aug 2016 · 2,773 MW · 174 23 Aug 2016 · 1,435 MW · 242 24 Aug 2016 · 1,138 MW · 175 25 Aug 2016 · 656 MW · 114 26 Aug 2016 · 1,512 MW · 98
15 Aug 17 Aug 19 Aug 21 Aug 22 Aug 23 Aug 25 Aug

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

The weather it burned in

33°high
46km/h · peak gust
13%lowest humidity

It had gone 16 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.

How big is it?

10 km
It burned the equivalent of 11% of the area of London (174 km² against 1,583 km²).

London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).

This compares size, not location: both shapes are at the same scale, north up, centred on each other.

What happened to each town

  1. Dzhangil`dinskiy Жангелді ауданы where it started
    10,760 ha reached on 16 Aug
    0.3 %
  2. Naurzumskiy Наурызым ауданы
    6,870 ha reached on 15 Aug
    0.4 %

Burnt area inside each municipality, from crossing the GWIS perimeter with administrative boundaries. The distance runs from the point marking the centre of each area to the nearest fire: staying a kilometre away does not mean it reached the houses.

People and buildings inside the perimeter

GHSL 2015
Built-up area< 0.1 ha
Residents< 20

Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2015, satellite-based estimate).

This is an estimate on 100 m cells, made from satellite imagery and census data: it does not mean that homes burned or that anyone was harmed. The perimeter also contains land that never burned.

Source: Global Human Settlement Layer (GHS-BUILT-S and GHS-POP R2023A), European Commission Joint Research Centre (JRC), © European Union, CC BY 4.0. Sum inside the perimeter computed by WorldFires. human-settlement.emergency.copernicus.eu

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)
15 Aug 31.9 °C 24 % 36 km/h 0.0 mm Very high 43
16 Aug 31.4 °C 30 % 35 km/h 0.1 mm Very high 40
17 Aug 29.9 °C 29 % 46 km/h 0.0 mm Very high 46
18 Aug 31.6 °C 21 % 35 km/h 0.0 mm Very high 41
19 Aug 31.1 °C 32 % 37 km/h 0.0 mm Very high 42
20 Aug 27.6 °C 28 % 46 km/h 0.0 mm Very high 47
21 Aug 25.5 °C 33 % 38 km/h 0.0 mm Very high 40
22 Aug 26.6 °C 24 % 24 km/h 0.0 mm High 30
23 Aug 28.8 °C 25 % 24 km/h 0.0 mm High 31
24 Aug 29.7 °C 18 % 23 km/h 0.0 mm High 35
25 Aug 31.5 °C 19 % 19 km/h 0.0 mm High 33
26 Aug 33.3 °C 13 % 26 km/h 0.0 mm Very high 48
27 Aug after 28.7 °C 28 % 36 km/h 0.6 mm Very high 40
28 Aug after 26.5 °C 28 % 37 km/h 0.2 mm Very high 44
29 Aug after 28.8 °C 21 % 55 km/h 0.0 mm Extreme 57
30 Aug after 19.7 °C 25 % 42 km/h 0.0 mm Very high 47
31 Aug after 22.8 °C 22 % 20 km/h 0.0 mm High 31
1 Sept after 26.6 °C 14 % 44 km/h 0.0 mm Extreme 54
2 Sept after 27.0 °C 15 % 42 km/h 0.0 mm Extreme 55
3 Sept after 21.9 °C 26 % 54 km/h 0.0 mm Extreme 57
4 Sept after 21.8 °C 45 % 59 km/h 0.6 mm Very high 41
5 Sept after 25.2 °C 33 % 42 km/h 0.0 mm High 33

Before and after, from space

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

Before · 8 Aug 2016
After · 2 Sept 2016

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 · 921Every 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 Dzhangil`dinskiy fire last?
According to the heat detections seen by satellite inside the perimeter, it burned from 15 August 2016 to 26 August 2016 (12 days). The perimeter dates it from 20 August 2016 to 26 August 2016.
How much area did it burn?
The perimeter GWIS (Copernicus) rebuilt from heat detections is 17,407 hectares (174.1 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Dzhangil`dinskiy (10,760 ha, 0.3 %); Naurzumskiy (6,870 ha, 0.4 %).
What was the weather like?
During the fire the temperature reached 33.3 °C, humidity dropped to 13 % and gusts hit 46 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 · Emergency number and official warnings ›

Satellite cross-check

History of this page · 1 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
  1. Start date: 20 August 2016 → 15 August 2016.

RSS Changes to this page

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.

How we know this
  • Perimeter: GWIS (Copernicus), rebuilt from heat detections rather than mapped on imagery; 2 polygons grouped in this page.
  • Dates adjusted with the VIIRS detections inside the perimeter, which said 20 August 2016 to 26 August 2016. 921 Suomi-NPP VIIRS detections on those dates.
  • We have not matched this page with any official record.
  • Weather: Copernicus ERA5 reanalysis at the fire location, in cells of about 25 km.
  • Built-up area and population come from the JRC Global Human Settlement Layer (epoch 2015, 100 m cells), summed inside the perimeter: an estimate of what was there, not a damage count.

How we build fire pages: methodology ›

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.