Djema fire, 31 December 2022 Djema
The fire started on 31 December 2022 in Djema, Central African Republic, and satellites saw it burning for 17 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 20,455 hectares from heat detections, spread across a single municipality.
It is the 57th largest in Haut-Mbomou since 2016 (of 298 with a page). Number 18 in Central African Republic in 2022, of 98.
Compare with…
Suggestions: Djema · 2020Djema · 2019Djema · 2021Djema · 2016
- Burnt area
- 20,455ha
- GWIS perimeter (Copernicus)
- Duration
- 17days
- 31 Dec 2022 – 16 Jan 2023
- Municipalities hit
- 1
- sub-prefectures
- Started on
- 31 Dec
- 2022
- Heat detections
- 1,111
- in a single hotspot: 58 MW
- Danger at start
- 50
- Extreme · FWI index
- Average daily power
- 328MW
- 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 more than two months without rain (1 mm or more) when it started.
This area had burned before
97% of the perimeter overlaps earlier fires recorded since 2016: 8,426 ha in 2016, 9,174 ha in 2017, 2,668 ha in 2018, 12,477 ha in 2019, 10,479 ha in 2020, 10,509 ha in 2021, 2,333 ha in 2022. Part of it burned more than once, so the yearly figures add up to more than the 19,836 ha that had burned before.
- 8,705 ha Djema fire, December 2020 41,255 ha in total; the hectares shown are those it shares with this fire
- 8,664 ha Djema fire, December 2019 73,476 ha in total; the hectares shown are those it shares with this fire
- 8,638 ha Djema fire, December 2021 25,845 ha in total; the hectares shown are those it shares with this fire
- 3,889 ha Djema fire, December 2016 24,716 ha in total; the hectares shown are those it shares with this fire
- 3,761 ha Raga fire, December 2016 7,208 ha in total; the hectares shown are those it shares with this fire
- 2,668 ha Djema fire, December 2018 83,573 ha in total; the hectares shown are those it shares with this fire
- 1,370 ha Raga fire, January 2022 7,258 ha in total; the hectares shown are those it shares with this fire
- 565 ha Djema fire, December 2017 9,109 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 started13,398 ha reached on 31 Dec0.4 %
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 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) |
|---|---|---|---|---|---|
| 31 Dec | 33.6 °C | 18 % | 39 km/h | 0.0 mm | Extreme 50 |
| 1 Jan | 33.5 °C | 18 % | 43 km/h | 0.0 mm | Extreme 52 |
| 2 Jan | 33.2 °C | 18 % | 41 km/h | 0.0 mm | Extreme 52 |
| 3 Jan | 33.2 °C | 18 % | 42 km/h | 0.0 mm | Extreme 51 |
| 4 Jan | 33.5 °C | 19 % | 41 km/h | 0.0 mm | Extreme 51 |
| 5 Jan | 33.0 °C | 18 % | 44 km/h | 0.0 mm | Extreme 53 |
| 6 Jan | 33.6 °C | 15 % | 38 km/h | 0.0 mm | Extreme 51 |
| 7 Jan | 33.5 °C | 15 % | 40 km/h | 0.0 mm | Extreme 52 |
| 8 Jan | 33.9 °C | 13 % | 37 km/h | 0.0 mm | Extreme 51 |
| 9 Jan | 34.7 °C | 11 % | 36 km/h | 0.0 mm | Extreme 50 |
| 10 Jan | 33.7 °C | 11 % | 42 km/h | 0.0 mm | Extreme 56 |
| 11 Jan | 33.3 °C | 12 % | 39 km/h | 0.0 mm | Extreme 54 |
| 12 Jan | 33.6 °C | 11 % | 37 km/h | 0.0 mm | Extreme 52 |
| 13 Jan | 33.6 °C | 13 % | 37 km/h | 0.0 mm | Extreme 53 |
| 14 Jan | 34.0 °C | 14 % | 39 km/h | 0.0 mm | Extreme 54 |
| 15 Jan | 34.0 °C | 12 % | 41 km/h | 0.0 mm | Extreme 55 |
| 16 Jan | 34.8 °C | 11 % | 41 km/h | 0.0 mm | Extreme 56 |
| 17 Jan after | 34.3 °C | 11 % | 41 km/h | 0.0 mm | Extreme 56 |
| 18 Jan after | 34.5 °C | 11 % | 42 km/h | 0.0 mm | Extreme 57 |
| 19 Jan after | 35.4 °C | 12 % | 37 km/h | 0.0 mm | Extreme 53 |
| 20 Jan after | 36.3 °C | 11 % | 42 km/h | 0.0 mm | Extreme 57 |
| 21 Jan after | 36.2 °C | 10 % | 44 km/h | 0.0 mm | Extreme 58 |
| 22 Jan after | 35.6 °C | 11 % | 38 km/h | 0.0 mm | Extreme 55 |
| 23 Jan after | 35.4 °C | 9 % | 37 km/h | 0.0 mm | Extreme 55 |
| 24 Jan after | 36.2 °C | 9 % | 38 km/h | 0.0 mm | Extreme 56 |
| 25 Jan after | 35.7 °C | 15 % | 36 km/h | 0.0 mm | Extreme 56 |
| 26 Jan after | 36.1 °C | 14 % | 27 km/h | 0.0 mm | Extreme 55 |
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 10 January 2023 the air beside the fire reached 113 µg/m³ of PM2.5. That day averaged 61: 4.1 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 · 1,111Every 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 · 10 km away
- 83,573 haDjema10 December 2018 · 35 days · 24 km away
- 67,907 haRaga27 December 2022 · 28 days · 24 km away
- 137,432 haDjema4 December 2016 · 40 days · 25 km away
- 67,410 haRaga14 December 2020 · 31 days · 29 km away
- 623,165 haDjema21 December 2025 · 51 days · 36 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 31 December 2022 to 16 January 2023 (17 days). The perimeter dates it from 2 January 2023 to 16 January 2023.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 20,455 hectares (204.6 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Djema (13,398 ha, 0.4 %).
- What was the weather like?
- During the fire the temperature reached 34.8 °C, humidity dropped to 11 % and gusts hit 44 km/h. The fire danger index (FWI) reached 56, 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 2 January 2023 to 16 January 2023. 1,111 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 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.