Djema fire, 17 January 2024 Djema
The fire started on 17 January 2024 in Djema, Central African Republic, and satellites saw it burning for 18 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 7,911 hectares from heat detections, spread across a single municipality.
It is the 159th largest in Haut-Mbomou since 2016 (of 298 with a page). Number 36 in Central African Republic in 2024, of 87.
Compare with…
Suggestions: Djema · 2018Djema · 2019Djema · 2017Raga · 2021
- Burnt area
- 7,911ha
- GWIS perimeter (Copernicus)
- Duration
- 18days
- 17 Jan 2024 – 3 Feb 2024
- Municipalities hit
- 1
- sub-prefectures
- Started on
- 17 Jan
- 2024
- Heat detections
- 314
- in a single hotspot: 58 MW
- Danger at start
- 55
- Extreme · FWI index
- Average daily power
- 124MW
- 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 58 days without rain (1 mm or more) when it started.
This area had burned before
96% of the perimeter overlaps earlier fires recorded since 2016: 1,992 ha in 2016, 4,124 ha in 2017, 4,415 ha in 2018, 5,304 ha in 2019, 1,508 ha in 2020, 4,197 ha in 2021, 1,390 ha in 2022, 518 ha in 2023. Part of it burned more than once, so the yearly figures add up to more than the 7,617 ha that had burned before.
- 4,415 ha Djema fire, December 2018 83,573 ha in total; the hectares shown are those it shares with this fire
- 4,228 ha Djema fire, December 2019 73,476 ha in total; the hectares shown are those it shares with this fire
- 2,383 ha Djema fire, December 2017 9,493 ha in total; the hectares shown are those it shares with this fire
- 2,106 ha Raga fire, January 2021 8,509 ha in total; the hectares shown are those it shares with this fire
- 1,042 ha Djema fire, December 2020 23,574 ha in total; the hectares shown are those it shares with this fire
- 625 ha Raga fire, December 2016 7,208 ha in total; the hectares shown are those it shares with this fire
- 257 ha Djema fire, December 2022 8,644 ha in total; the hectares shown are those it shares with this fire
- 125 ha Djema fire, December 2016 137,432 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
-
Djema where it started5,920 ha reached on 17 Jan0.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 2025Inside 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
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) |
|---|---|---|---|---|---|
| 17 Jan | 33.9 °C | 9 % | 38 km/h | 0.0 mm | Extreme 55 |
| 18 Jan | 33.5 °C | 9 % | 35 km/h | 0.0 mm | Extreme 54 |
| 19 Jan | 34.0 °C | 8 % | 34 km/h | 0.0 mm | Extreme 53 |
| 20 Jan | 33.4 °C | 9 % | 41 km/h | 0.0 mm | Extreme 58 |
| 21 Jan | 33.8 °C | 8 % | 38 km/h | 0.0 mm | Extreme 56 |
| 22 Jan | 35.7 °C | 9 % | 29 km/h | 0.0 mm | Extreme 52 |
| 23 Jan | 35.1 °C | 10 % | 27 km/h | 0.0 mm | Extreme 51 |
| 24 Jan | 36.1 °C | 11 % | 36 km/h | 0.0 mm | Extreme 55 |
| 25 Jan | 35.8 °C | 13 % | 39 km/h | 0.0 mm | Extreme 59 |
| 26 Jan | 33.1 °C | 13 % | 44 km/h | 0.0 mm | Extreme 59 |
| 27 Jan | 33.1 °C | 12 % | 41 km/h | 0.0 mm | Extreme 59 |
| 28 Jan | 32.9 °C | 11 % | 41 km/h | 0.0 mm | Extreme 58 |
| 29 Jan | 33.9 °C | 12 % | 36 km/h | 0.0 mm | Extreme 55 |
| 30 Jan | 35.1 °C | 12 % | 38 km/h | 0.0 mm | Extreme 57 |
| 31 Jan | 34.1 °C | 10 % | 42 km/h | 0.0 mm | Extreme 60 |
| 1 Feb | 33.0 °C | 11 % | 44 km/h | 0.0 mm | Extreme 62 |
| 2 Feb | 32.8 °C | 12 % | 42 km/h | 0.0 mm | Extreme 60 |
| 3 Feb | 34.0 °C | 10 % | 36 km/h | 0.0 mm | Extreme 57 |
| 4 Feb after | 34.5 °C | 10 % | 40 km/h | 0.0 mm | Extreme 58 |
| 5 Feb after | 33.4 °C | 11 % | 41 km/h | 0.0 mm | Extreme 61 |
| 6 Feb after | 31.7 °C | 12 % | 44 km/h | 0.0 mm | Extreme 61 |
| 7 Feb after | 34.1 °C | 10 % | 42 km/h | 0.0 mm | Extreme 60 |
| 8 Feb after | 36.1 °C | 11 % | 33 km/h | 0.0 mm | Extreme 54 |
| 9 Feb after | 37.8 °C | 12 % | 36 km/h | 0.0 mm | Extreme 54 |
| 10 Feb after | 37.7 °C | 13 % | 26 km/h | 0.0 mm | Extreme 53 |
| 11 Feb after | 37.8 °C | 12 % | 34 km/h | 0.0 mm | Extreme 54 |
| 12 Feb after | 38.5 °C | 10 % | 34 km/h | 0.0 mm | Extreme 53 |
| 13 Feb after | 38.9 °C | 9 % | 34 km/h | 0.0 mm | Extreme 54 |
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.
The smoke
CAMS · CopernicusOn 22 January 2024 the air beside the fire reached 91 µg/m³ of PM2.5. That day averaged 44: 2.9 times the WHO daily guideline (15).
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)
Detections table · 314Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 73,476 haDjema12 December 2019 · 28 days · 0 km away
- 83,573 haDjema8 December 2018 · 37 days · 15 km away
- 623,165 haDjema21 December 2025 · 51 days · 28 km away
- 137,432 haDjema4 December 2016 · 40 days · 28 km away
- 67,410 haRaga8 December 2020 · 42 days · 30 km away
- 67,907 haRaga20 December 2022 · 42 days · 32 km away
Frequently asked questions
- How long did the Djema fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 17 January 2024 to 3 February 2024 (18 days). The perimeter dates it from 17 January 2024 to 30 January 2024.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 7,911 hectares (79.1 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Djema (5,920 ha, 0.2 %).
- What was the weather like?
- During the fire the temperature reached 36.1 °C, humidity dropped to 8 % and gusts hit 44 km/h. The fire danger index (FWI) reached 62, class Extreme.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Central African Republic (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 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 adjusted with the VIIRS detections inside the perimeter, which said 17 January 2024 to 30 January 2024. 314 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 2025, 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 ADM3 (Creative Commons Attribution 3.0 Intergovernmental Organisations (CC BY 3.0 IGO)). 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.