Skip to content
worldfires
KZ · Kazakhstan · →

Borodulikhinskiy fire, September 2016 Borodulikhinskiy

Out · last detection 28 Sept 2016, 07:18 UTC

The fire started on 24 September 2016 in Borodulikhinskiy, Kazakhstan, and satellites saw it burning for 5 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 9,643 hectares from heat detections, spread across a single municipality.

It is the 16th largest in East Kazakhstan Region since 2016 (of 92 with a page). Number 4 in Kazakhstan in 2016, of 36.

Burnt area
9,643ha
GWIS perimeter (Copernicus)
Duration
5days
24 Sept 2016 – 28 Sept 2016
Municipalities hit
1
districts
Started on
24 Sept
2016
Heat detections
446
in a single hotspot: 189 MW
Danger at start
26
High · FWI index
Energy released
6.7GW
sum of detected power

Where it burned

28 Sept 2016
HOTSPOTS BY DAY 24 Sept28 Sept

How it evolved, day by day

2425262728

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

The weather it burned in

20°high
53km/h · peak gust
24%lowest humidity

It had gone 10 days without rain (1 mm or more) when it started. Rain came after the fire: 2.7 mm on 30 Sept.

This area had burned before

No earlier perimeters overlap this fire since 2016, when the satellite record begins.

What happened to each town

  1. Borodulikhinskiy where it started
    9,710 ha reached on 24 Sept
    1.6 %

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)
24 Sept 17.7 °C 33 % 47 km/h 0.0 mm High 26
25 Sept 19.7 °C 25 % 53 km/h 0.0 mm High 33
26 Sept 19.3 °C 28 % 37 km/h 0.0 mm High 28
27 Sept 17.8 °C 32 % 19 km/h 0.0 mm High 22
28 Sept 20.3 °C 24 % 20 km/h 0.0 mm High 24
29 Sept after 20.9 °C 39 % 26 km/h 0.0 mm High 23
30 Sept after 21.4 °C 45 % 34 km/h 2.7 mm Low 7

Before and after, from space

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

Before · 17 Sept 2016
After · 5 Oct 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 · 446Every 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 Borodulikhinskiy fire last?
GWIS (Copernicus) dates it between 24 September 2016 and 28 September 2016: 5 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 9,643 hectares (96.4 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Borodulikhinskiy (9,710 ha, 1.6 %).
What was the weather like?
During the fire the temperature reached 20.3 °C, humidity dropped to 24 % and gusts hit 53 km/h. The fire danger index (FWI) reached 33, class 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.