Skip to content
worldfires
RU · Russia · →

Khangalassky Ulus fire, 23 July 2019 Khangalassky Ulus

Out · last detection 1 Aug 2019, 03:13 UTC

The fire started on 23 July 2019 in Khangalassky Ulus, Russia, and satellites saw it burning for 10 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 3,234 hectares from heat detections, spread across a single municipality.

It is the 1336th largest in Sakha Republic since 2016 (of 1422 with a page). Number 559 in Russia in 2019, of 610.

Compare with…
Burnt area
3,234ha
GWIS perimeter (Copernicus)
Duration
10days
23 Jul 2019 – 1 Aug 2019
Municipalities hit
1
districts
Started on
23 Jul
2019
Heat detections
697
in a single hotspot: 168 MW
Danger at start
16
Moderate · FWI index
Average daily power
692MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 23 Jul1 Aug
1 Aug 2019

How it evolved, day by day

23 Jul 2019 · 16 MW · 7 24 Jul 2019 · 402 MW · 47 25 Jul 2019 · 434 MW · 63 26 Jul 2019 · 415 MW · 91 27 Jul 2019 · 1,773 MW · 169 28 Jul 2019 · 3,088 MW · 195 29 Jul 2019 · 354 MW · 41 30 Jul 2019 · 215 MW · 36 31 Jul 2019 · 215 MW · 46 1 Aug 2019 · 10 MW · 2
23 Jul 25 Jul 27 Jul 28 Jul 29 Jul 31 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

31°high
44km/h · peak gust
27%lowest humidity

It had gone 5 days without rain (1 mm or more) when it started. Rain came after the fire: 13.2 mm on 3 Aug.

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 2% of the area of London (32 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. Khangalassky Ulus where it started
    3,213 ha reached on 23 Jul
    0.1 %

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 2020
Built-up area< 0.1 ha
Residents< 20

Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2020, 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)
16 Jul 25.1 °C 29 % 33 km/h 0.0 mm Moderate 16
17 Jul 27.0 °C 34 % 34 km/h 0.0 mm Moderate 17
18 Jul 18.9 °C 58 % 44 km/h 3.4 mm Very low 2
19 Jul 16.0 °C 57 % 34 km/h 0.3 mm Very low 3
20 Jul 18.9 °C 37 % 25 km/h 0.0 mm Low 7
21 Jul 23.1 °C 34 % 19 km/h 0.0 mm Low 10
22 Jul 27.1 °C 36 % 26 km/h 0.0 mm Moderate 14
23 Jul 25.7 °C 29 % 27 km/h 0.0 mm Moderate 16
24 Jul 27.6 °C 30 % 21 km/h 0.0 mm Moderate 18
25 Jul 27.7 °C 31 % 24 km/h 0.0 mm Moderate 18
26 Jul 28.7 °C 27 % 23 km/h 0.0 mm Moderate 20
27 Jul 30.6 °C 28 % 20 km/h 0.0 mm High 22
28 Jul 30.4 °C 32 % 23 km/h 0.0 mm High 22
29 Jul 29.8 °C 35 % 36 km/h 0.0 mm High 28
30 Jul 22.9 °C 37 % 39 km/h 0.0 mm High 23
31 Jul 22.6 °C 35 % 21 km/h 0.0 mm Moderate 20
1 Aug 20.3 °C 51 % 34 km/h 2.6 mm Very low 4
2 Aug after 18.5 °C 61 % 26 km/h 0.2 mm Low 6
3 Aug after 20.3 °C 83 % 54 km/h 13.2 mm Very low 0

Before and after, from space

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

Before · 16 Jul 2019
After · 8 Aug 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 · 697Every 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 Russia ›

Frequently asked questions

How long did the Khangalassky Ulus fire last?
GWIS (Copernicus) dates it between 23 July 2019 and 1 August 2019: 10 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 3,234 hectares (32.3 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Khangalassky Ulus (3,213 ha, 0.1 %).
What was the weather like?
During the fire the temperature reached 30.6 °C, humidity dropped to 27 % and gusts hit 44 km/h. The fire danger index (FWI) reached 28, class High.
Where does this data come from?
From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Russia (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 from the perimeter: the VIIRS detections inside it did not change them. 697 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 2020, 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.