Djema fire, 1 February 2022 Djema, Yalinga, Rafaï
The fire started on 1 February 2022 in Djema, Central African Republic, and satellites saw it burning for 31 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 63,846 hectares from heat detections, spread across 3 municipalities.
It is the 18th largest in Haut-Mbomou since 2016 (of 298 with a page). Number 10 in Central African Republic in 2022, of 97.
Compare with…
Suggestions: Djema · 2020Yalinga · 2021Djema · 2018Djema · 2020
- Burnt area
- 63,846ha
- GWIS perimeter (Copernicus)
- Duration
- 31days
- 1 Feb 2022 – 3 Mar 2022
- Municipalities hit
- 3
- sub-prefectures
- Started on
- 1 Feb
- 2022
- Heat detections
- 2,241
- in a single hotspot: 229 MW
- Danger at start
- 57
- Extreme · FWI index
- Average daily power
- 478MW
- 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
99% of the perimeter overlaps earlier fires recorded since 2016: 32,557 ha in 2016, 6,613 ha in 2017, 20,280 ha in 2018, 28,702 ha in 2019, 62,276 ha in 2020, 33,739 ha in 2021. Part of it burned more than once, so the yearly figures add up to more than the 62,981 ha that had burned before.
- 35,208 ha Djema fire, January 2020 307,099 ha in total; the hectares shown are those it shares with this fire
- 33,145 ha Yalinga fire, January 2021 207,292 ha in total; the hectares shown are those it shares with this fire
- 17,898 ha Djema fire, December 2018 111,967 ha in total; the hectares shown are those it shares with this fire
- 13,707 ha Djema fire, January 2020 45,397 ha in total; the hectares shown are those it shares with this fire
- 13,188 ha Yalinga fire, December 2020 261,604 ha in total; the hectares shown are those it shares with this fire
- 7,665 ha Yalinga fire, January 2019 9,516 ha in total; the hectares shown are those it shares with this fire
- 4,185 ha Djema fire, March 2019 5,624 ha in total; the hectares shown are those it shares with this fire
- 4,048 ha Yalinga fire, January 2018 5,002 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 started31,817 ha reached on 1 Feb0.9 %
-
29,205 ha reached on 3 Feb0.7 %
-
3,191 ha reached on 26 Feb0.1 %
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) |
|---|---|---|---|---|---|
| 5 Feb | 33.6 °C | 11 % | 35 km/h | 0.0 mm | Extreme 57 |
| 6 Feb | 33.5 °C | 10 % | 39 km/h | 0.0 mm | Extreme 58 |
| 7 Feb | 34.6 °C | 8 % | 38 km/h | 0.0 mm | Extreme 58 |
| 8 Feb | 36.3 °C | 7 % | 37 km/h | 0.0 mm | Extreme 57 |
| 9 Feb | 37.3 °C | 8 % | 29 km/h | 0.0 mm | Extreme 53 |
| 10 Feb | 37.8 °C | 9 % | 38 km/h | 0.0 mm | Extreme 57 |
| 11 Feb | 37.4 °C | 8 % | 39 km/h | 0.0 mm | Extreme 60 |
| 12 Feb | 37.7 °C | 9 % | 37 km/h | 0.0 mm | Extreme 59 |
| 13 Feb | 38.0 °C | 8 % | 36 km/h | 0.0 mm | Extreme 58 |
| 14 Feb | 38.2 °C | 7 % | 39 km/h | 0.0 mm | Extreme 60 |
| 15 Feb | 38.0 °C | 5 % | 31 km/h | 0.0 mm | Extreme 57 |
| 16 Feb | 36.8 °C | 7 % | 23 km/h | 0.0 mm | Extreme 57 |
| 17 Feb | 37.7 °C | 7 % | 21 km/h | 0.0 mm | Extreme 55 |
| 18 Feb | 38.3 °C | 6 % | 23 km/h | 0.0 mm | Extreme 55 |
| 19 Feb | 37.5 °C | 6 % | 36 km/h | 0.0 mm | Extreme 68 |
| 20 Feb | 35.5 °C | 8 % | 35 km/h | 0.0 mm | Extreme 67 |
| 21 Feb | 35.6 °C | 8 % | 37 km/h | 0.0 mm | Extreme 64 |
| 22 Feb | 37.1 °C | 7 % | 29 km/h | 0.0 mm | Extreme 58 |
| 23 Feb | 37.9 °C | 7 % | 23 km/h | 0.0 mm | Extreme 54 |
| 24 Feb | 38.6 °C | 7 % | 27 km/h | 0.0 mm | Extreme 56 |
| 25 Feb | 38.1 °C | 5 % | 40 km/h | 0.0 mm | Extreme 65 |
| 26 Feb | 37.6 °C | 7 % | 40 km/h | 0.0 mm | Extreme 67 |
| 27 Feb | 38.6 °C | 8 % | 37 km/h | 0.0 mm | Extreme 64 |
| 28 Feb | 39.1 °C | 7 % | 42 km/h | 0.0 mm | Extreme 68 |
| 1 Mar | 38.4 °C | 7 % | 37 km/h | 0.0 mm | Extreme 66 |
| 2 Mar | 38.6 °C | 7 % | 27 km/h | 0.0 mm | Extreme 58 |
| 3 Mar | 36.3 °C | 23 % | 42 km/h | 0.0 mm | Extreme 54 |
| 4 Mar after | 37.6 °C | 22 % | 32 km/h | 0.0 mm | Very high 47 |
| 5 Mar after | 39.7 °C | 13 % | 27 km/h | 0.0 mm | Very high 46 |
| 6 Mar after | 40.0 °C | 9 % | 28 km/h | 0.0 mm | Extreme 50 |
| 7 Mar after | 39.0 °C | 14 % | 28 km/h | 0.0 mm | Extreme 52 |
| 8 Mar after | 36.9 °C | 20 % | 38 km/h | 0.0 mm | Extreme 54 |
| 9 Mar after | 37.6 °C | 19 % | 40 km/h | 0.0 mm | Extreme 56 |
| 10 Mar after | 39.5 °C | 17 % | 33 km/h | 0.0 mm | Extreme 51 |
| 11 Mar after | 37.8 °C | 21 % | 31 km/h | 0.0 mm | Extreme 56 |
| 12 Mar after | 37.2 °C | 11 % | 26 km/h | 0.0 mm | Very high 48 |
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 · 2,241Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
Frequently asked questions
- How long did the Djema fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 1 February 2022 to 3 March 2022 (31 days). The perimeter dates it from 5 February 2022 to 2 March 2022.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 63,846 hectares (638.5 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 3 municipalities: Djema (31,817 ha, 0.9 %); Yalinga (29,205 ha, 0.7 %); Rafaï (3,191 ha, 0.1 %).
- What was the weather like?
- During the fire the temperature reached 39.1 °C, humidity dropped to 5 % and gusts hit 42 km/h. The fire danger index (FWI) reached 68, 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; 3 polygons grouped in this page.
- Dates adjusted with the VIIRS detections inside the perimeter, which said 5 February 2022 to 2 March 2022. 2,241 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.