Otrarskiy fire, June 2016 Kazakhstan
The fire started on 13 June 2016 in Otrarskiy, Kazakhstan, and satellites saw it burning for 1 day. Copernicus’s global GWIS system rebuilt a burnt perimeter of 4,681 hectares from heat detections, spread across a single municipality.
Number 18 in Kazakhstan in 2016, of 36.
Compare with…
We have the GWIS perimeter for this fire, but the VIIRS sensors did not capture it in enough detail: no day-by-day evolution, but the split by municipality is there.
- Burnt area
- 4,681ha
- GWIS perimeter (Copernicus)
- Duration
- 1day
- 13 Jun 2016 – 13 Jun 2016
- Municipalities hit
- 0
- districts
- Started on
- 13 Jun
- 2016
- Danger at start
- 79
- Very extreme · FWI index
Where it burned
The weather it burned in
It had gone 8 days without rain (1 mm or more) when it started. Rain came after the fire: 5.7 mm on 16 Jun.
This area had burned before
No earlier perimeters overlap this fire since 2016, when the satellite record begins.
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.
People and buildings inside the perimeter
GHSL 2015Inside 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) |
|---|---|---|---|---|---|
| 13 Jun | 39.3 °C | 17 % | 50 km/h | 0.0 mm | Very extreme 79 |
| 14 Jun after | 34.3 °C | 27 % | 63 km/h | 0.0 mm | Very extreme 92 |
| 15 Jun after | 27.6 °C | 36 % | 57 km/h | 0.0 mm | Extreme 54 |
| 16 Jun after | 26.4 °C | 50 % | 37 km/h | 5.7 mm | Low 6 |
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
If the day is cloudy, change the date: each satellite passes once a day. In false colour the burnt ground looks brown or red.
Frequently asked questions
- How long did the Otrarskiy fire last?
- GWIS (Copernicus) dates it between 13 June 2016 and 13 June 2016: 1 day 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 4,681 hectares (46.8 km²). It is an estimate: official national figures may differ.
- What was the weather like?
- During the fire the temperature reached 39.3 °C, humidity dropped to 17 % and gusts hit 50 km/h. The fire danger index (FWI) reached 79, 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 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
No changes since 24 October 2026.
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 from the perimeter: the VIIRS detections inside it did not change them. No 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.