Burned area
satellite only56,255ha
Perimeter published by GWIS (Copernicus).
- Source
- GWIS (Copernicus)
- Date
- 14 Aug 2017 – 19 Aug 2017
+− cross-check
No official record is matched to this page to compare it with.
KZ · Kazakhstan · –
Bayganinskiy fire, 14 August 2017 Байғанин ауданы · Bayganinskiy
Out · last detection 19 Aug 2017, 09:04 UTC
The fire started on 14 August 2017 in Bayganinskiy, Kazakhstan, and satellites saw it burning for 6 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 56,255 hectares from heat detections, spread across a single municipality.
It is the largest fire in Aktobe Region since 2016 (of 99 with a page). Number 3 in Kazakhstan in 2017, of 239.
Use this data
Compare with…
Use this data
Fire page data · version 2026-10-25matches the official recordwith caveatssatellite onlymodel
When copying, the sentence is
Tick the figures you want: they make up the lede and the CSV.
Duration by satellite
satellite only6days
14 Aug 2017 to 19 Aug 2017: first and last day with fire on the page.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- last detection: 19 Aug 2017, 09:04 UTC
+− cross-check
Satellites pass a few times a day and cloud or smoke can hide the fire: a lack of detections is not an official extinction. Each country’s emergency service declares a fire contained or out.
Start
satellite only14 Aug 2017
First day with fire seen by the satellites or the perimeter.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 14 Aug 2017
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Hotspots
satellite only2,487
VIIRS detections at 375 m. Most intense hotspot: 448 MW.
- Source
- NASA FIRMS · VIIRS (Suomi NPP)
- Date
- 14 Aug 2017 – 19 Aug 2017
+− cross-check
There is no official record to compare with. Each hotspot is a pixel detected in one satellite pass, not a separate fire.
The worst day
satellite only27,210MW
Total radiative power on 15 August 2017; hotspots that day: 1,128.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 15 Aug 2017
+− cross-check
Fire radiative power (FRP) measures the energy the fire gives off when the satellite passes. Added up by day, it compares intensity, not area.
Danger at the start
model48.3FWI · very high
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 12.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 14 Aug 2017, local noon
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
This is an index computed from weather model data, not a measurement of the fire nor an official warning. Danger warnings are issued by each country’s authority. Emergency number and official warnings
Weather during the fire
model33.0°C · 14% RH
High of 33.0 °C and minimum humidity of 14% on 18 August 2017; gusts of 47 km/h on 15 August 2017.
- Source
- weather model at the fire’s grid cell
- Date
- 14 Aug 2017 – 19 Aug 2017
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
These are model values for a cell of about 25 km, not from a weather station: they may differ from what was measured on the ground.
Living inside
model≈ 150people
Estimated residents inside the perimeter and 3.8 ha of built-up area (100 m grid, epoch 2015).
- Source
- GHSL R2023A · JRC
- Date
- calculated on 24 October 2026
+− cross-check
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.
This page’s change log has been kept since 24 October 2026: every night what it publishes is compared and the difference is logged. Anything earlier is reconstructed from each source’s date and marked as reconstructed.
Show
-
· reconstructed weatherWeather and FWI computed from the ERA5 reanalysis
-
logLast day with fire: 18 August 2017 → 19 August 2017.
-
· reconstructed GHSLPopulation and built-up area computed
What was saved on 25 October 2026
Every night a snapshot of what the page shows is saved. If anything changes, it appears in the list as a log entry.
- Area
- 56,255 ha
- Dates
- 14 Aug 2017 – 19 Aug 2017
- Name
- Bayganinskiy
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/bayganinskiy-2017-08-3?v=2026-10-25A version keeps the area, dates, name and official record; the area as it was logged (changes under 2% are not logged). The map, hotspots and weather always show today’s data.
Citation
A lede of about 60 words figures only, no adjectives
CSV for this fire bayganinskiy-2017-08-3.csv · daily, no individual hotspots
| fecha | focos_viirs | frp_mw | tmax_c | tmin_c | hr_min_pct | viento_max_kmh | racha_max_kmh | precip_mm | fwi | clase_fwi | dentro_del_incendio |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2017-08-14 | 319 | 1,207 | 29 | 18.7 | 23 | 21.4 | 38.2 | 0 | 48.3 | muy_alto | 1 |
| 2017-08-15 | 1,128 | 27,210 | 30.3 | 15.7 | 17 | 28.9 | 46.8 | 0 | 61.7 | extremo | 1 |
| 2017-08-16 | 775 | 12,291 | 32.1 | 17.7 | 13 | 19.7 | 38.2 | 0 | 64.5 | extremo | 1 |
| 2017-08-17 | 230 | 2,922 | 31.9 | 16.7 | 16 | 15.3 | 31.7 | 0 | 51 | extremo | 1 |
| 2017-08-18 | 32 | 1,735 | 33 | 18.9 | 14 | 17.3 | 29.2 | 0 | 37.4 | alto | 1 |
| 2017-08-19 | 3 | 11 | 30.8 | 19.6 | 16 | 25.4 | 46.1 | 0 | 75.5 | muy_extremo | 1 |
| 2017-08-20 | 0 | 0 | 31.8 | 16.1 | 15 | 22.7 | 41.8 | 0 | 61.3 | extremo | 0 |
| 2017-08-21 | 0 | 0 | 32.4 | 17.6 | 14 | 10.7 | 24.5 | 0 | 48.5 | muy_alto | 0 |
| 2017-08-22 | 0 | 0 | 34.2 | 17.4 | 12 | 16.2 | 32 | 0 | 54.1 | extremo | 0 |
| 2017-08-23 | 0 | 0 | 33.4 | 19 | 13 | 24.9 | 45.4 | 0 | 83.4 | muy_extremo | 0 |
| 2017-08-24 | 0 | 0 | 35 | 19.3 | 14 | 20.2 | 39.2 | 0 | 72.6 | muy_extremo | 0 |
| 2017-08-25 | 0 | 0 | 35 | 19.9 | 14 | 15.5 | 29.5 | 0 | 59.6 | extremo | 0 |
| 2017-08-26 | 0 | 0 | 34.2 | 18.6 | 15 | 12.4 | 20.9 | 0 | 49.3 | muy_alto | 0 |
| 2017-08-27 | 0 | 0 | 33.4 | 23.4 | 17 | 18.4 | 37.4 | 0 | 51.7 | extremo | 0 |
| 2017-08-28 | 0 | 0 | 30.7 | 17.2 | 18 | 16.9 | 33.8 | 0 | 59.6 | extremo | 0 |
| 2017-08-29 | 0 | 0 | 33.7 | 16.5 | 13 | 14.6 | 28.1 | 0 | 53.1 | extremo | 0 |
It is generated in your browser from this page’s data: one file per fire, aggregated by day and without individual hotspots.
Live widget for your story
It updates itself while the fire is still active and links to this page. Free, with the attribution shown at the bottom.
Sources for this page: GWIS (Copernicus), NASA FIRMS (VIIRS), ERA5 (ECMWF/Copernicus C3S) · Open-Meteo.com (CC BY 4.0), GHSL (JRC). Open-Meteo.com · How we build fire pages: methodology
- Burnt area
- 56,255ha
- GWIS perimeter (Copernicus)
- Duration
- 6days
- 14 Aug 2017 – 19 Aug 2017
- Municipalities hit
- 1
- districts
- Started on
- 14 Aug
- 2017
- Heat detections
- 2,487
- in a single hotspot: 448 MW
- Danger at start
- 48
- Very high · FWI index
- Average daily power
- 7.6GW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
14 Aug19 Aug
19 Aug 2017
How it evolved, day by day
15 Aug
18 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
47km/h · peak gust
13%lowest humidity
It had gone 12 days without rain (1 mm or more) when it started.
This area had burned before
0% of the perimeter overlaps earlier fires recorded since 2016: 227 ha in 2016.
How big is it?
London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).
Paris boundary: geoBoundaries · Institut national de l'information géographique et forestière (IGN-F) (Etalab Open License 2.0).
Madrid boundary: geoBoundaries · Open Data ESRI, IGN Central Registry of Cartography Area (CC BY 4.0).
Berlin boundary: geoBoundaries · Federal Agency for Cartography and Geodesy (dl-de/by-2-0).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each town
-
57,042 ha reached on 14 Aug0.9 %
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 2015Built-up area3.8 ha
Residents≈ 150
Inside the perimeter there were about 3.8 hectares of built-up land and about 150 residents (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) |
|---|---|---|---|---|---|
| 14 Aug | 29.0 °C | 23 % | 38 km/h | 0.0 mm | Very high 48 |
| 15 Aug | 30.3 °C | 17 % | 47 km/h | 0.0 mm | Extreme 62 |
| 16 Aug | 32.1 °C | 13 % | 38 km/h | 0.0 mm | Extreme 64 |
| 17 Aug | 31.9 °C | 16 % | 32 km/h | 0.0 mm | Extreme 51 |
| 18 Aug | 33.0 °C | 14 % | 29 km/h | 0.0 mm | High 37 |
| 19 Aug | 30.8 °C | 16 % | 46 km/h | 0.0 mm | Very extreme 76 |
| 20 Aug after | 31.8 °C | 15 % | 42 km/h | 0.0 mm | Extreme 61 |
| 21 Aug after | 32.4 °C | 14 % | 24 km/h | 0.0 mm | Very high 48 |
| 22 Aug after | 34.2 °C | 12 % | 32 km/h | 0.0 mm | Extreme 54 |
| 23 Aug after | 33.4 °C | 13 % | 45 km/h | 0.0 mm | Very extreme 83 |
| 24 Aug after | 35.0 °C | 14 % | 39 km/h | 0.0 mm | Very extreme 73 |
| 25 Aug after | 35.0 °C | 14 % | 30 km/h | 0.0 mm | Extreme 60 |
| 26 Aug after | 34.2 °C | 15 % | 21 km/h | 0.0 mm | Very high 49 |
| 27 Aug after | 33.4 °C | 17 % | 37 km/h | 0.0 mm | Extreme 52 |
| 28 Aug after | 30.7 °C | 18 % | 34 km/h | 0.0 mm | Extreme 60 |
| 29 Aug after | 33.7 °C | 13 % | 28 km/h | 0.0 mm | Extreme 53 |
Its twins: fires that started in the same weather
It started with an FWI of 48.3, a minimum humidity of 23% and 12 days without rain. Fires in the area that started in weather like this since 2016: 11.
FWI at the start
48.3
Minimum humidity
23 %
Days without rain
12
this fire
chosen twins
rest of the area
Almost identicalSimilar
Outlines of the closest twins
This fire · Bayganinskiy fire, 14 August 2017
56,255 ha
6 days
FWI 48.3
Min. humidity 23 %
Temirskiy fire, August 2017
5,343 ha
4 days
FWI 47.7
Min. humidity 24 %
187 km away, in 2017
First rain (1 mm or more) after it ended: none in the following ten days.
Bayganinskiy fire, July 2018
6,966 ha
2 days
FWI 49.1
Min. humidity 20 %
131 km away, in 2018
First rain (1 mm or more) after it ended: 1.5 mm on 5 Aug.
Bayganinskiy fire, August 2016
5,790 ha
4 days
FWI 50.9
Min. humidity 20 %
19 km away, in 2016
First rain (1 mm or more) after it ended: none in the following ten days.
Mugalzharskiy fire, August 2018
5,220 ha
5 days
FWI 49.3
Min. humidity 20 %
79 km away, in 2018
First rain (1 mm or more) after it ended: 2.1 mm on 14 Aug.
Temirskiy fire, August 2016
5,886 ha
3 days
FWI 47.2
Min. humidity 18 %
100 km away, in 2016
First rain (1 mm or more) after it ended: none in the following ten days.
What happened to them
Fires in the area that started in similar weather: 11. With fewer than 15 we give no figures: they would be more noise than signal.
This is a bank of analogues: it shows what usually happens, not what will happen. With fewer than 15 twins we give no figures. How we calculate it
How it ended
—first rain
—no rain in ten days
47km/h · max. gust
It was considered over on 19 Aug, and not even 1 mm fell in the following ten days: it went out without rain.
Weather on this page: Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)
How a twin is chosen
- Same area: fires that have already ended, less than 250 km from this one, since 2016.
- Same start: we compare the FWI on the first day, the minimum humidity that day and the run of days without rain before it. The slider sets how much they may differ.
- Only pages with final weather data (ERA5 reanalysis) calculated in the same way as this fire’s; agricultural and grass burns and pages with data under review are left out.
- Fires burning at the same time as this one (a week before or after) are left out: they share the same spell of weather and do not count as a precedent.
- They are sorted by similarity, and the outlines of the first five are drawn.
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
↔
Before · 7 Aug 2017
After · 26 Aug 2017
Sentinel-2 did not pass over on that day. Try another date, or use false colour, which is daily.
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 · 2,487Every 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 time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
Frequently asked questions
- How long did the Bayganinskiy fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 14 August 2017 to 19 August 2017 (6 days). The perimeter dates it from 14 August 2017 to 18 August 2017.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 56,255 hectares (562.6 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Bayganinskiy (57,042 ha, 0.9 %).
- What was the weather like?
- During the fire the temperature reached 33.0 °C, humidity dropped to 13 % and gusts hit 47 km/h. The fire danger index (FWI) reached 76, class Very 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.
- Last day with fire: 18 August 2017 → 19 August 2017.
RSS Changes to this page With cross-checks and a citable version
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
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 14 August 2017 to 18 August 2017. 2,487 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.
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.