Skip to content
worldfires
KZ · Kazakhstan · →

Urdinskiy fire, June 2019 Urdinskiy

Out · last detection 23 Jun 2019, 10:26 UTC

The fire started on 22 June 2019 in Urdinskiy, Kazakhstan, and satellites saw it burning for 3 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 4,879 hectares from heat detections, spread across a single municipality.

It is the 31th largest in West Kazakhstan Region since 2016 (of 59 with a page). Number 84 in Kazakhstan in 2019, of 163.

Burnt area
4,879ha
GWIS perimeter (Copernicus)
Duration
3days
22 Jun 2019 – 24 Jun 2019
Municipalities hit
1
districts
Started on
22 Jun
2019
Heat detections
151
in a single hotspot: 278 MW
Danger at start
59
Extreme · FWI index
Energy released
3.2GW
sum of detected power

Where it burned

23 Jun 2019
HOTSPOTS BY DAY 22 Jun24 Jun

How it evolved, day by day

2223

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
41km/h · peak gust
11%lowest humidity

It had gone 4 days without rain (1 mm or more) when it started. Rain came after the fire: 1.9 mm on 2 Jul.

This area had burned before

3% of the perimeter overlaps earlier fires recorded since 2016: 18 ha in 2017, 151 ha in 2018.

What happened to each town

  1. Urdinskiy where it started
    4,844 ha reached on 22 Jun
    0.2 %

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)
22 Jun 35.0 °C 12 % 41 km/h 0.0 mm Extreme 59
23 Jun 35.7 °C 12 % 40 km/h 0.0 mm Extreme 58
24 Jun 37.6 °C 11 % 36 km/h 0.0 mm Extreme 58
25 Jun after 35.2 °C 18 % 40 km/h 0.9 mm Extreme 60
26 Jun after 30.3 °C 16 % 42 km/h 0.0 mm Extreme 52
27 Jun after 30.1 °C 18 % 23 km/h 0.0 mm Very high 42
28 Jun after 35.3 °C 10 % 59 km/h 0.0 mm Very extreme 81
29 Jun after 30.1 °C 21 % 40 km/h 0.0 mm Extreme 54
30 Jun after 25.1 °C 28 % 36 km/h 0.3 mm Very high 43
1 Jul after 21.6 °C 37 % 47 km/h 0.0 mm Very high 44
2 Jul after 34.3 °C 21 % 66 km/h 1.9 mm Extreme 56

Before and after, from space

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

Before · 15 Jun 2019
After · 1 Jul 2019

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 · 151Every 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 Urdinskiy fire last?
GWIS (Copernicus) dates it between 22 June 2019 and 24 June 2019: 3 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 4,879 hectares (48.8 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Urdinskiy (4,844 ha, 0.2 %).
What was the weather like?
During the fire the temperature reached 37.6 °C, humidity dropped to 11 % and gusts hit 41 km/h. The fire danger index (FWI) reached 59, 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

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.