Skip to content
worldfires
AZ · Azerbaijan · →

Kalbajar District fire, January 2023 Kalbajar District

Out · last measured on 3 Jan 2023

The fire started on 1 January 2023 in Kalbajar District, Azerbaijan, and satellites saw it burning for 3 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 749 hectares from heat detections, spread across a single municipality.

It is the 175th largest in Contiguous Azerbaijan since 2016 (of 308 with a page). The largest in Azerbaijan in 2023, of 4.

Compare with…

We have the GWIS perimeter for this fire, but the VIIRS sensors did not capture it in enough detail: no day-by-day evolution, but the split by municipality is there.

Burnt area
749ha
GWIS perimeter (Copernicus)
Duration
3days
1 Jan 2023 – 3 Jan 2023
Municipalities hit
1
districts
Started on
1 Jan
2023

Where it burned

This area had burned before

51% of the perimeter overlaps earlier fires recorded since 2016: 379 ha in 2017.

How big is it?

10 km
It burned the equivalent of 0.5% of the area of London (7.5 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. Kalbajar District where it started
    749 ha
    0.3 %

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

Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2025, 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. The GHSL 2025 epoch is a projection made from 2020 and earlier data.

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

Before and after, from space

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

Before · 25 Dec 2022
After · 10 Jan 2023

If the day is cloudy, change the date: each satellite passes once a day. In false colour the burnt ground looks brown or red.

The smoke

CAMS · Copernicus

On 2 January 2023 the air beside the fire reached 48 µg/m³ of PM2.5. That day averaged 20: 1.3 times the WHO daily guideline (15).

PM2.5 peak48 µg/m³
Days over the guideline2 days
PM1069 µg/m³
Optical depth0.13
3031123456
Good Fair Moderate Poor Very poor Extremely poor

Particles from the Copernicus CAMS model at the centre of the perimeter; these are not measurements in each town. The pale bar is the worst hour, the solid one the daily average.

Open-Meteo.com (CC BY 4.0) · Copernicus Atmosphere Monitoring Service (CAMS)

Other fires nearby

All fires in Azerbaijan ›

Frequently asked questions

How long did the Kalbajar District fire last?
GWIS (Copernicus) dates it between 1 January 2023 and 3 January 2023: 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 749 hectares (7.5 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Kalbajar District (749 ha, 0.3 %).
Where does this data come from?
From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Azerbaijan (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 · 2 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
  1. Start date: 31 December 2022 → 1 January 2023.
  2. Start date: 1 January 2023 → 31 December 2022.

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. No Suomi-NPP VIIRS detections on those dates.
  • We have not matched this page with any official record.
  • Built-up area and population come from the JRC Global Human Settlement Layer (epoch 2025, 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 (Creative Commons Attribution-ShareAlike 3.0 Unported). 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.