Skip to content
worldfires
RU · Russia · →

Aldansky Ulus fire, 23 July 2019 Aldansky Ulus

Out · last detection 3 Aug 2019, 18:05 UTC

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

It is the 925th largest in Sakha Republic since 2016 (of 1422 with a page). Number 336 in Russia in 2019, of 613.

Burnt area
5,089ha
GWIS perimeter (Copernicus)
Duration
12days
23 Jul 2019 – 3 Aug 2019
Municipalities hit
1
districts
Started on
23 Jul
2019
Heat detections
473
in a single hotspot: 165 MW
Danger at start
9
Low · FWI index
Energy released
2.8GW
sum of detected power

Where it burned

3 Aug 2019
HOTSPOTS BY DAY 23 Jul3 Aug

How it evolved, day by day

232425262728293031123

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

The weather it burned in

28°high
44km/h · peak gust
29%lowest humidity

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

This area had burned before

No earlier perimeters overlap this fire since 2016, when the satellite record begins.

What happened to each town

  1. Aldansky Ulus where it started
    4,862 ha reached on 23 Jul
    0.0 %

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)
23 Jul 19.3 °C 34 % 39 km/h 0.0 mm Low 9
24 Jul 19.2 °C 37 % 43 km/h 0.0 mm Low 11
25 Jul 18.7 °C 29 % 29 km/h 0.0 mm Low 11
26 Jul 19.8 °C 52 % 16 km/h 0.0 mm Low 8
27 Jul 22.8 °C 44 % 27 km/h 0.2 mm Low 10
28 Jul 25.8 °C 33 % 24 km/h 0.0 mm Moderate 13
29 Jul 27.5 °C 29 % 17 km/h 0.0 mm Moderate 15
30 Jul 21.1 °C 49 % 38 km/h 0.0 mm Moderate 15
31 Jul 19.3 °C 48 % 28 km/h 0.0 mm Moderate 12
1 Aug 22.0 °C 38 % 20 km/h 0.0 mm Moderate 12
2 Aug 21.4 °C 47 % 44 km/h 2.6 mm Very low 4
3 Aug 23.3 °C 40 % 41 km/h 0.0 mm Low 11
4 Aug after 18.0 °C 67 % 50 km/h 21.1 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 · 10 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 · 473Every 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

Frequently asked questions

How long did the Aldansky Ulus fire last?
GWIS (Copernicus) dates it between 23 July 2019 and 3 August 2019: 12 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 5,089 hectares (50.9 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Aldansky Ulus (4,862 ha, 0.0 %).
What was the weather like?
During the fire the temperature reached 27.5 °C, humidity dropped to 29 % and gusts hit 44 km/h. The fire danger index (FWI) reached 15, class Moderate.
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

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.