Skip to content
worldfires
KZ · Kazakhstan · →

Ulytauskiy fire, 4 July 2017 Ұлытау ауданы · Ulytauskiy

Out · last detection 9 Jul 2017, 22:27 UTC

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

It is the 74th largest in Karaganda Region since 2016 (of 222 with a page). Number 79 in Kazakhstan in 2017, of 239.

Compare with…
Burnt area
6,814ha
GWIS perimeter (Copernicus)
Duration
6days
4 Jul 2017 – 9 Jul 2017
Municipalities hit
1
districts
Started on
4 Jul
2017
Heat detections
275
in a single hotspot: 85 MW
Danger at start
71
Very extreme · FWI index
Average daily power
606MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 4 Jul9 Jul
9 Jul 2017

How it evolved, day by day

4 Jul 2017 · 93 MW · 3 5 Jul 2017 · 2 MW · 2 6 Jul 2017 · 263 MW · 11 7 Jul 2017 · 83 MW · 17 8 Jul 2017 · 3,015 MW · 222 9 Jul 2017 · 182 MW · 20
4 Jul 5 Jul 6 Jul 7 Jul 8 Jul 9 Jul

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

The weather it burned in

40°high
59km/h · peak gust
13%lowest humidity

It had gone 10 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 4.3% of the area of London (68 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. Ulytauskiy Ұлытау ауданы where it started
    6,689 ha reached on 4 Jul
    0.0 %

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)
4 Jul 39.5 °C 16 % 48 km/h 0.0 mm Very extreme 71
5 Jul 36.9 °C 18 % 45 km/h 0.0 mm Extreme 60
6 Jul 40.5 °C 14 % 52 km/h 1.4 mm Very extreme 71
7 Jul 33.2 °C 13 % 40 km/h 0.0 mm Extreme 60
8 Jul 35.8 °C 13 % 29 km/h 0.0 mm Extreme 53
9 Jul 32.2 °C 20 % 59 km/h 0.0 mm Very extreme 73
10 Jul after 29.4 °C 14 % 45 km/h 0.0 mm Extreme 59
11 Jul after 28.1 °C 26 % 39 km/h 0.7 mm High 37
12 Jul after 28.1 °C 23 % 44 km/h 0.1 mm Very high 44
13 Jul after 22.5 °C 44 % 42 km/h 0.9 mm High 25
14 Jul after 24.7 °C 24 % 41 km/h 0.0 mm Very high 39
15 Jul after 27.9 °C 19 % 27 km/h 0.0 mm High 38
16 Jul after 28.3 °C 17 % 42 km/h 0.0 mm Extreme 50
17 Jul after 28.6 °C 19 % 39 km/h 0.0 mm Very high 48
18 Jul after 29.8 °C 24 % 46 km/h 0.0 mm Extreme 53
19 Jul after 30.6 °C 19 % 29 km/h 0.0 mm Very high 43

Before and after, from space

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

Before · 27 Jun 2017
After · 16 Jul 2017

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 · 275Every 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 Ulytauskiy fire last?
According to the heat detections seen by satellite inside the perimeter, it burned from 4 July 2017 to 9 July 2017 (6 days). The perimeter dates it from 6 July 2017 to 9 July 2017.
How much area did it burn?
The perimeter GWIS (Copernicus) rebuilt from heat detections is 6,814 hectares (68.1 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Ulytauskiy (6,689 ha, 0.0 %).
What was the weather like?
During the fire the temperature reached 40.5 °C, humidity dropped to 13 % and gusts hit 59 km/h. The fire danger index (FWI) reached 73, 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.

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 6 July 2017 to 9 July 2017. 275 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.