Skip to content
worldfires
KZ · Kazakhstan · →

Balkhashskiy fire, April 2022 Balkhashskiy

Out · last detection 22 Apr 2022, 21:12 UTC

The fire started on 14 April 2022 in Balkhashskiy, Kazakhstan, and satellites saw it burning for 9 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 6,438 hectares from heat detections, spread across a single municipality.

It is the 15th largest in Almaty Region since 2016 (of 36 with a page). Number 12 in Kazakhstan in 2022, of 42.

Burnt area
6,438ha
GWIS perimeter (Copernicus)
Duration
9days
14 Apr 2022 – 22 Apr 2022
Municipalities hit
1
districts
Started on
14 Apr
2022
Heat detections
407
in a single hotspot: 206 MW
Danger at start
29
High · FWI index
Energy released
8.1GW
sum of detected power

Where it burned

22 Apr 2022
HOTSPOTS BY DAY 14 Apr22 Apr

How it evolved, day by day

141516171819202122

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

The weather it burned in

26°high
56km/h · peak gust
9%lowest humidity

It had gone 14 days without rain (1 mm or more) when it started. Rain came after the fire: 5.7 mm on 24 Apr.

This area had burned before

38% of the perimeter overlaps earlier fires recorded since 2016: 245 ha in 2016, 2,174 ha in 2021.

What happened to each town

  1. Balkhashskiy where it started
    6,546 ha reached on 13 Apr
    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)
13 Apr 21.0 °C 9 % 38 km/h 0.0 mm High 29
14 Apr 21.6 °C 9 % 40 km/h 0.0 mm High 32
15 Apr 21.3 °C 16 % 49 km/h 0.0 mm High 36
16 Apr 22.1 °C 15 % 46 km/h 0.0 mm High 36
17 Apr 22.0 °C 17 % 38 km/h 0.0 mm High 31
18 Apr 25.5 °C 11 % 32 km/h 0.0 mm High 32
19 Apr 18.6 °C 37 % 56 km/h 0.0 mm High 34
20 Apr 16.6 °C 29 % 41 km/h 0.0 mm High 28
21 Apr 20.5 °C 31 % 36 km/h 0.0 mm High 26
22 Apr 22.4 °C 32 % 30 km/h 0.0 mm High 24
23 Apr after 21.5 °C 43 % 46 km/h 0.2 mm High 26
24 Apr after 15.0 °C 53 % 62 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.

Before · 7 Apr 2022
After · 29 Apr 2022

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 · 407Every 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 Balkhashskiy fire last?
GWIS (Copernicus) dates it between 14 April 2022 and 22 April 2022: 9 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 6,438 hectares (64.4 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Balkhashskiy (6,546 ha, 0.2 %).
What was the weather like?
During the fire the temperature reached 25.5 °C, humidity dropped to 9 % and gusts hit 56 km/h. The fire danger index (FWI) reached 36, class High.
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.