Topchikhinsky District fire, April 2016 Topchikhinsky District
The fire started on 18 April 2016 in Topchikhinsky District, Russia, and satellites saw it burning for 3 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 3,247 hectares from heat detections, spread across a single municipality.
It is the 23th largest in Altai Krai since 2016 (of 26 with a page). Number 637 in Russia in 2016, of 692.
Compare with…
- Burnt area
- 3,247ha
- GWIS perimeter (Copernicus)
- Duration
- 3days
- 18 Apr 2016 – 20 Apr 2016
- Municipalities hit
- 1
- districts
- Started on
- 18 Apr
- 2016
- Heat detections
- 100
- in a single hotspot: 168 MW
- Danger at start
- 8
- Low · FWI index
- Average daily power
- 650MW
- detected power per day, on average
Where it burned
How it evolved, day by day
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
It had gone 4 days without rain (1 mm or more) when it started. Rain came after the fire: 4.6 mm on 22 Apr.
This area had burned before
No earlier perimeters overlap this fire since 2016, when the satellite record begins.
How big is it?
London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).
Moscow boundary: geoBoundaries · OpenStreetMap, Wambacher · © OpenStreetMap contributors (ODbL 1.0).
Paris boundary: geoBoundaries · Institut national de l'information géographique et forestière (IGN-F) (Etalab Open License 2.0).
Madrid boundary: geoBoundaries · Open Data ESRI, IGN Central Registry of Cartography Area (CC BY 4.0).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each town
-
Topchikhinsky District where it started3,242 ha1.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.
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) |
|---|---|---|---|---|---|
| 18 Apr | 17.1 °C | 40 % | 30 km/h | 0.1 mm | Low 8 |
| 19 Apr | 24.1 °C | 19 % | 40 km/h | 0.0 mm | Moderate 14 |
| 20 Apr | 25.6 °C | 31 % | 24 km/h | 0.2 mm | Moderate 13 |
| 21 Apr after | 26.4 °C | 18 % | 27 km/h | 0.0 mm | Moderate 15 |
| 22 Apr after | 20.5 °C | 44 % | 29 km/h | 4.6 mm | Very low 1 |
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
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 · 100Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Frequently asked questions
- How long did the Topchikhinsky District fire last?
- GWIS (Copernicus) dates it between 18 April 2016 and 20 April 2016: 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 3,247 hectares (32.5 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Topchikhinsky District (3,242 ha, 1.0 %).
- What was the weather like?
- During the fire the temperature reached 25.6 °C, humidity dropped to 19 % and gusts hit 40 km/h. The fire danger index (FWI) reached 14, 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 · 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.
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
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. 100 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.
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.