Burned area
satellite only516ha
Perimeter published by GWIS (Copernicus).
- Source
- GWIS (Copernicus)
- Date
- 24 Dec 2019 – 25 Dec 2019
+− cross-check
No official record is matched to this page to compare it with.
AZ · Azerbaijan · –
Kalbajar District fire, 24 December 2019 Kalbajar District
Out · last detection 25 Dec 2019, 10:55 UTC
The fire started on 24 December 2019 in Kalbajar District, Azerbaijan, and satellites saw it burning for 2 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 516 hectares from heat detections, spread across a single municipality.
It is the 263th largest in Contiguous Azerbaijan since 2016 (of 278 with a page). Number 71 in Azerbaijan in 2019, of 74.
The power measured by the satellite is low (27.2 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.
Use this data
Compare with…
Use this data
Fire page data · version 2026-10-24matches the official recordwith caveatssatellite onlymodel
When copying, the sentence is
Tick the figures you want: they make up the lede and the CSV.
Duration by satellite
satellite only2days
24 Dec 2019 to 25 Dec 2019: first and last day with fire on the page.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- last detection: 25 Dec 2019, 10:55 UTC
+− cross-check
Satellites pass a few times a day and cloud or smoke can hide the fire: a lack of detections is not an official extinction. Each country’s emergency service declares a fire contained or out.
Start
satellite only24 Dec 2019
First day with fire seen by the satellites or the perimeter.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 24 Dec 2019
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Hotspots
satellite only17
VIIRS detections at 375 m. Most intense hotspot: 27 MW.
- Source
- NASA FIRMS · VIIRS (Suomi NPP)
- Date
- 24 Dec 2019 – 25 Dec 2019
+− cross-check
There is no official record to compare with. Each hotspot is a pixel detected in one satellite pass, not a separate fire.
The worst day
satellite only206MW
Total radiative power on 25 December 2019; hotspots that day: 15.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 25 Dec 2019
+− cross-check
Fire radiative power (FRP) measures the energy the fire gives off when the satellite passes. Added up by day, it compares intensity, not area.
Danger at the start
model0.6FWI · very low
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 6.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 24 Dec 2019, local noon
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
This is an index computed from weather model data, not a measurement of the fire nor an official warning. Danger warnings are issued by each country’s authority. Emergency number and official warnings
Weather during the fire
model7.3°C · 39% RH
High of 7.3 °C and minimum humidity of 39% on 25 December 2019; gusts of 37 km/h on 25 December 2019.
- Source
- weather model at the fire’s grid cell
- Date
- 24 Dec 2019 – 25 Dec 2019
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
These are model values for a cell of about 25 km, not from a weather station: they may differ from what was measured on the ground.
This page’s change log has been kept since 24 October 2026: every night what it publishes is compared and the difference is logged. Anything earlier is reconstructed from each source’s date and marked as reconstructed.
Show
-
· reconstructed weatherWeather and FWI computed from the ERA5 reanalysis
-
· reconstructed GHSLPopulation and built-up area computed
What was saved on 24 October 2026
Every night a snapshot of what the page shows is saved. If anything changes, it appears in the list as a log entry.
- Area
- 516 ha
- Dates
- 24 Dec 2019 – 25 Dec 2019
- Name
- Kalbajar District
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/kalbajar-district-2019-12-2?v=2026-10-24A version keeps the area, dates, name and official record; the area as it was logged (changes under 2% are not logged). The map, hotspots and weather always show today’s data.
Citation
A lede of about 60 words figures only, no adjectives
CSV for this fire kalbajar-district-2019-12-2.csv · daily, no individual hotspots
| fecha | focos_viirs | frp_mw | tmax_c | tmin_c | hr_min_pct | viento_max_kmh | racha_max_kmh | precip_mm | fwi | clase_fwi | dentro_del_incendio |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2019-12-24 | 2 | 16 | 7 | -5.8 | 36 | 9 | 31.7 | 0 | 0.6 | muy_bajo | 1 |
| 2019-12-25 | 15 | 206 | 7.3 | -5.5 | 39 | 8.6 | 36.7 | 0 | 0.7 | muy_bajo | 1 |
| 2019-12-26 | 0 | 0 | 7.6 | -3.4 | 29 | 8.7 | 39.2 | 0 | 0.8 | muy_bajo | 0 |
| 2019-12-27 | 0 | 0 | 2.7 | -3.1 | 62 | 6.5 | 29.9 | 0.7 | 0.6 | muy_bajo | 0 |
| 2019-12-28 | 0 | 0 | 2.8 | -2.3 | 60 | 6.5 | 23.4 | 2.6 | 0.1 | muy_bajo | 0 |
It is generated in your browser from this page’s data: one file per fire, aggregated by day and without individual hotspots.
Live widget for your story
It updates itself while the fire is still active and links to this page. Free, with the attribution shown at the bottom.
Sources for this page: GWIS (Copernicus), NASA FIRMS (VIIRS), ERA5 (ECMWF/Copernicus C3S) · Open-Meteo.com (CC BY 4.0), GHSL (JRC). Open-Meteo.com · How we build fire pages: methodology
- Burnt area
- 516ha
- GWIS perimeter (Copernicus)
- Duration
- 2days
- 24 Dec 2019 – 25 Dec 2019
- Municipalities hit
- 1
- districts
- Started on
- 24 Dec
- 2019
- Heat detections
- 17
- in a single hotspot: 27 MW
- Danger at start
- 1
- Very low · FWI index
- Average daily power
- 110MW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
24 Dec25 Dec
25 Dec 2019
How it evolved, day by day
24 Dec
25 Dec
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
7°high
37km/h · peak gust
36%lowest humidity
It had gone 6 days without rain (1 mm or more) when it started. Rain came after the fire: 2.6 mm on 28 Dec.
This area had burned before
70% of the perimeter overlaps earlier fires recorded since 2016: 362 ha in 2017.
How big is it?
London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.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).
Berlin boundary: geoBoundaries · Federal Agency for Cartography and Geodesy (dl-de/by-2-0).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each town
-
Kalbajar District where it started517 ha reached on 24 Dec0.2 %
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 2020Built-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) |
|---|---|---|---|---|---|
| 24 Dec | 7.0 °C | 36 % | 32 km/h | 0.0 mm | Very low 1 |
| 25 Dec | 7.3 °C | 39 % | 37 km/h | 0.0 mm | Very low 1 |
| 26 Dec after | 7.6 °C | 29 % | 39 km/h | 0.0 mm | Very low 1 |
| 27 Dec after | 2.7 °C | 62 % | 30 km/h | 0.7 mm | Very low 1 |
| 28 Dec after | 2.8 °C | 60 % | 23 km/h | 2.6 mm | Very low 0 |
Its twins: fires that started in the same weather
It started with an FWI of 0.6, a minimum humidity of 36% and 6 days without rain. Fires in the area that started in weather like this since 2016: 16.
FWI at the start
0.6
Minimum humidity
36 %
Days without rain
6
this fire
chosen twins
rest of the area
Almost identicalSimilar
Outlines of the closest twins
This fire · Kalbajar District fire, 24 December 2019
516 ha
2 days
FWI 0.6
Min. humidity 36 %
Kapan fire, November 2016
814 ha
2 days
FWI 0.7
Min. humidity 37 %
101 km away, in 2016
First rain (1 mm or more) after it ended: 4.3 mm on 1 Dec.
Sisian fire, November 2019
387 ha
5 days
FWI 2.5
Min. humidity 35 %
58 km away, in 2019
First rain (1 mm or more) after it ended: 1.3 mm on 21 Nov.
Kapan fire, November 2016
390 ha
2 days
FWI 0.6
Min. humidity 34 %
100 km away, in 2016
First rain (1 mm or more) after it ended: 2.3 mm on 1 Dec.
Sisian fire, November 2019
513 ha
4 days
FWI 3.4
Min. humidity 35 %
61 km away, in 2019
First rain (1 mm or more) after it ended: 1.3 mm on 21 Nov.
Doğubayazıt fire, July 2018
108 ha
1 day
FWI 0.9
Min. humidity 36 %
171 km away, in 2018
First rain (1 mm or more) after it ended: 2.7 mm on 31 Jul.
What happened to them
- 2 days
- median duration
- 440 ha
- median area
- 6 %
- went past 1,000 ha
- 2.3 mm
- rain at the end (median; 15 of 16 had it)
It burned an area similar to its twins (516 ha against a median of 440 ha) and lasted 2 days, against 2 days.
In 1 of 16, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 2.3 mm.
This is a bank of analogues: it shows what usually happens, not what will happen. With fewer than 15 twins we give no figures. How we calculate it
How it ended
2.6 mmfirst rain
28 Dec3 days after it ended
37km/h · max. gust
It was considered over on 25 Dec, and on 28 Dec 2.6 mm fell. We do not know whether the rain or the firefighters put it out. Twins with rain when they ended: 15 of 16, with a median of 2.3 mm.
Weather on this page: Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)
How a twin is chosen
- Same area: fires that have already ended, less than 250 km from this one, since 2016.
- Same start: we compare the FWI on the first day, the minimum humidity that day and the run of days without rain before it. The slider sets how much they may differ.
- Only pages with final weather data (ERA5 reanalysis) calculated in the same way as this fire’s; agricultural and grass burns and pages with data under review are left out.
- Fires burning at the same time as this one (a week before or after) are left out: they share the same spell of weather and do not count as a precedent.
- They are sorted by similarity, and the outlines of the first five are drawn.
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
↔
Before · 17 Dec 2019
After · 1 Jan 2020
Sentinel-2 did not pass over on that day. Try another date, or use false colour, which is daily.
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 · 17Every 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 time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 6,490 haKalbajar District25 November 2025 · 8 days · 22 km away
- 2,573 haLachin DistrictSeptember 2017 · 5 days · 23 km away
- 10,567 haKalbajar District2 September 2017 · 20 days · 26 km away
- 1,684 haTartar District26 October 2020 · 10 days · 26 km away
- 5,352 haGoranboy DistrictOctober 2020 · 12 days · 32 km away
- 2,733 haTartar DistrictJuly 2026 · 5 days · 39 km away
Frequently asked questions
- How long did the Kalbajar District fire last?
- GWIS (Copernicus) dates it between 24 December 2019 and 25 December 2019: 2 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 516 hectares (5.2 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Kalbajar District (517 ha, 0.2 %).
- What was the weather like?
- During the fire the temperature reached 7.3 °C, humidity dropped to 36 % and gusts hit 37 km/h. The fire danger index (FWI) reached 1, class Very low.
- 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.
- How did the fires that started in similar weather in this area end?
- Fires less than 250 km away that started since 2016 with a similar FWI, humidity and dry spell: 16. Their median duration was 2 days and their median area 440 ha; 6 % went past 1,000 ha. In 1 of 16, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 2.3 mm.
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 With cross-checks and a citable version
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. 17 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.
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.