Skip to content
worldfires
KZ · Kazakhstan · →

Bayganinskiy fire, 6 August 2016 Байғанин ауданы · Bayganinskiy

Out · last detection 9 Aug 2016, 09:36 UTC

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

It is the 29th largest in Aktobe Region since 2016 (of 101 with a page). Number 9 in Kazakhstan in 2016, of 36.

Compare with…

Suggestions: Bayganinskiy · 2017

Burnt area
5,790ha
GWIS perimeter (Copernicus)
Duration
4days
6 Aug 2016 – 9 Aug 2016
Municipalities hit
1
districts
Started on
6 Aug
2016
Heat detections
303
in a single hotspot: 101 MW
Danger at start
50
Extreme · FWI index
Average daily power
813MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 6 Aug9 Aug
9 Aug 2016

How it evolved, day by day

6 Aug 2016 · 153 MW · 39 7 Aug 2016 · 1,375 MW · 66 8 Aug 2016 · 847 MW · 106 9 Aug 2016 · 879 MW · 92
6 Aug 7 Aug 8 Aug 9 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

38°high
33km/h · peak gust
15%lowest humidity

It had gone 9 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 3.7% of the area of London (58 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. Bayganinskiy Байғанин ауданы where it started
    5,855 ha reached on 6 Aug
    0.1 %

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)
5 Aug 36.8 °C 17 % 31 km/h 0.0 mm Extreme 50
6 Aug 36.2 °C 20 % 33 km/h 0.0 mm Extreme 51
7 Aug 36.8 °C 18 % 26 km/h 0.0 mm Very high 46
8 Aug 37.8 °C 17 % 24 km/h 0.0 mm Very high 48
9 Aug 36.7 °C 15 % 30 km/h 0.0 mm Extreme 51
10 Aug after 36.7 °C 12 % 30 km/h 0.0 mm Very high 49
11 Aug after 37.4 °C 15 % 31 km/h 0.0 mm Extreme 50
12 Aug after 37.1 °C 17 % 31 km/h 0.0 mm Extreme 55
13 Aug after 36.4 °C 16 % 35 km/h 0.0 mm Extreme 54
14 Aug after 34.7 °C 18 % 37 km/h 0.0 mm Extreme 55
15 Aug after 34.8 °C 15 % 35 km/h 0.0 mm Extreme 54
16 Aug after 36.1 °C 11 % 30 km/h 0.0 mm Extreme 52
17 Aug after 35.6 °C 20 % 39 km/h 0.0 mm Extreme 56
18 Aug after 35.7 °C 19 % 41 km/h 0.0 mm Extreme 59
19 Aug after 35.1 °C 16 % 37 km/h 0.0 mm Extreme 56

Before and after, from space

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

Before · 30 Jul 2016
After · 16 Aug 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 · 303Every 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 Bayganinskiy fire last?
According to the heat detections seen by satellite inside the perimeter, it burned from 6 August 2016 to 9 August 2016 (4 days). The perimeter dates it from 7 August 2016 to 9 August 2016.
How much area did it burn?
The perimeter GWIS (Copernicus) rebuilt from heat detections is 5,790 hectares (57.9 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Bayganinskiy (5,855 ha, 0.1 %).
What was the weather like?
During the fire the temperature reached 37.8 °C, humidity dropped to 15 % and gusts hit 33 km/h. The fire danger index (FWI) reached 51, 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 · 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: 7 August 2016 → 6 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.
  • Dates adjusted with the VIIRS detections inside the perimeter, which said 7 August 2016 to 9 August 2016. 303 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.