Kaev Seima fire, 23 December 2019 Kaev Seima, Pech Chreada
The fire started on 23 December 2019 in Kaev Seima, Cambodia, and satellites saw it burning for 15 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 4,846 hectares from heat detections, spread across 2 municipalities.
It is the 25th largest in Mondulkiri since 2016 (of 112 with a page). Number 13 in Cambodia in 2019, of 66.
Compare with…
- Burnt area
- 4,846ha
- GWIS perimeter (Copernicus)
- Duration
- 15days
- 23 Dec 2019 – 6 Jan 2020
- Municipalities hit
- 2
- districts
- Started on
- 23 Dec
- 2019
- Heat detections
- 197
- in a single hotspot: 48 MW
- Danger at start
- 19
- Moderate · FWI index
- Average daily power
- 96MW
- 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 42 days without rain (1 mm or more) when it started.
This area had burned before
66% of the perimeter overlaps earlier fires recorded since 2016: 522 ha in 2016, 1,906 ha in 2017, 3,569 ha in 2018. Part of it burned more than once, so the yearly figures add up to more than the 3,204 ha that had burned before.
- 1,627 ha Kaev Seima fire, December 2018 3,072 ha in total; the hectares shown are those it shares with this fire
- 972 ha Pech Chreada fire, February 2017 3,034 ha in total; the hectares shown are those it shares with this fire
- 934 ha Kaev Seima fire, January 2017 2,559 ha in total; the hectares shown are those it shares with this fire
- 475 ha Pech Chreada fire, January 2016 24,939 ha in total; the hectares shown are those it shares with this fire
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
-
Kaev Seima where it started4,671 ha reached on 23 Dec1.6 %
-
209 ha reached on 27 Dec0.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.
People and buildings inside the perimeter
GHSL 2020Inside the perimeter there were about 0.06 hectares of built-up land and about 20 residents (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) |
|---|---|---|---|---|---|
| 25 Dec | 33.4 °C | 38 % | 25 km/h | 0.0 mm | Moderate 19 |
| 26 Dec | 32.1 °C | 48 % | 19 km/h | 0.0 mm | Moderate 17 |
| 27 Dec | 32.2 °C | 42 % | 39 km/h | 0.0 mm | High 23 |
| 28 Dec | 32.3 °C | 40 % | 43 km/h | 0.0 mm | High 24 |
| 29 Dec | 32.5 °C | 47 % | 35 km/h | 0.0 mm | Moderate 21 |
| 30 Dec | 33.9 °C | 45 % | 31 km/h | 0.0 mm | High 22 |
| 31 Dec | 33.2 °C | 41 % | 48 km/h | 0.0 mm | High 27 |
| 1 Jan | 33.5 °C | 41 % | 50 km/h | 0.0 mm | High 28 |
| 2 Jan | 34.0 °C | 45 % | 46 km/h | 0.0 mm | High 27 |
| 3 Jan | 33.0 °C | 42 % | 41 km/h | 0.0 mm | High 28 |
| 4 Jan | 31.7 °C | 43 % | 44 km/h | 0.0 mm | High 27 |
| 5 Jan | 32.6 °C | 39 % | 45 km/h | 0.0 mm | High 28 |
| 6 Jan | 33.5 °C | 40 % | 28 km/h | 0.0 mm | High 24 |
| 7 Jan after | 34.1 °C | 44 % | 31 km/h | 0.0 mm | High 26 |
| 8 Jan after | 35.2 °C | 40 % | 37 km/h | 0.0 mm | High 28 |
| 9 Jan after | 34.5 °C | 42 % | 39 km/h | 0.0 mm | High 28 |
| 10 Jan after | 34.5 °C | 37 % | 25 km/h | 0.0 mm | High 25 |
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 · 197Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 6,724 haKaev Seima14 January 2026 · 22 days · 4 km away
- 24,939 haPech Chreada11 January 2016 · 39 days · 9 km away
- 6,507 haKaev Seima14 January 2026 · 22 days · 21 km away
- 15,165 haKaev Seima10 January 2026 · 33 days · 28 km away
- 36,542 haSnuol14 January 2016 · 87 days · 32 km away
- 11,261 haChetr Borei24 December 2021 · 23 days · 40 km away
Frequently asked questions
- How long did the Kaev Seima fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 23 December 2019 to 6 January 2020 (15 days). The perimeter dates it from 25 December 2019 to 31 December 2019.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 4,846 hectares (48.5 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Kaev Seima (4,671 ha, 1.6 %); Pech Chreada (209 ha, 0.0 %).
- What was the weather like?
- During the fire the temperature reached 33.9 °C, humidity dropped to 38 % and gusts hit 48 km/h. The fire danger index (FWI) reached 27, class High.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Cambodia (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.
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.
- Last day with fire: 31 December 2019 → 6 January 2020.
- Start date: 25 December 2019 → 23 December 2019.
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 adjusted with the VIIRS detections inside the perimeter, which said 25 December 2019 to 31 December 2019. 197 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 4.0 International (CC BY 4.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.