Yalinga fire, 2 January 2023 Yalinga, Djema
The fire started on 2 January 2023 in Yalinga, Central African Republic, and satellites saw it burning for 21 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 40,751 hectares from heat detections, spread across 2 municipalities.
It is the 41th largest in Haute-Kotto since 2016 (of 373 with a page). Number 6 in Central African Republic in 2023, of 58.
Compare with…
- Burnt area
- 40,751ha
- GWIS perimeter (Copernicus)
- Duration
- 21days
- 2 Jan 2023 – 22 Jan 2023
- Municipalities hit
- 2
- sub-prefectures
- Started on
- 2 Jan
- 2023
- Heat detections
- 1,881
- in a single hotspot: 0 MW
- Danger at start
- 54
- Extreme · FWI index
- Average daily power
- 547MW
- 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
98% of the perimeter overlaps earlier fires recorded since 2016: 29,140 ha in 2016, 17,039 ha in 2017, 14,333 ha in 2018, 8,296 ha in 2019, 49,563 ha in 2020, 994 ha in 2021, 21,538 ha in 2022. Part of it burned more than once, so the yearly figures add up to more than the 40,019 ha that had burned before.
- 32,728 ha Yalinga fire, December 2020 261,604 ha in total; the hectares shown are those it shares with this fire
- 14,632 ha Yalinga fire, December 2017 42,902 ha in total; the hectares shown are those it shares with this fire
- 12,926 ha Djema fire, January 2020 45,397 ha in total; the hectares shown are those it shares with this fire
- 8,132 ha Yalinga fire, January 2022 11,705 ha in total; the hectares shown are those it shares with this fire
- 7,834 ha Djema fire, December 2018 111,967 ha in total; the hectares shown are those it shares with this fire
- 6,092 ha Yalinga fire, December 2018 71,520 ha in total; the hectares shown are those it shares with this fire
- 4,420 ha Yalinga fire, February 2022 8,818 ha in total; the hectares shown are those it shares with this fire
- 4,327 ha Yalinga fire, January 2016 12,226 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
-
Yalinga where it started40,754 ha1.0 %
-
217 ha0.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 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) |
|---|---|---|---|---|---|
| 2 Jan | 34.6 °C | 17 % | 40 km/h | 0.0 mm | Extreme 54 |
| 3 Jan | 34.6 °C | 17 % | 41 km/h | 0.0 mm | Extreme 54 |
| 4 Jan | 34.5 °C | 18 % | 41 km/h | 0.0 mm | Extreme 54 |
| 5 Jan | 34.3 °C | 18 % | 42 km/h | 0.0 mm | Extreme 56 |
| 6 Jan | 34.7 °C | 15 % | 37 km/h | 0.0 mm | Extreme 53 |
| 7 Jan | 34.8 °C | 14 % | 38 km/h | 0.0 mm | Extreme 54 |
| 8 Jan | 34.8 °C | 13 % | 34 km/h | 0.0 mm | Extreme 51 |
| 9 Jan | 35.6 °C | 11 % | 34 km/h | 0.0 mm | Extreme 51 |
| 10 Jan | 34.6 °C | 11 % | 34 km/h | 0.0 mm | Extreme 52 |
| 11 Jan | 34.5 °C | 12 % | 36 km/h | 0.0 mm | Extreme 54 |
| 12 Jan | 34.4 °C | 12 % | 33 km/h | 0.0 mm | Extreme 52 |
| 13 Jan | 34.7 °C | 13 % | 35 km/h | 0.0 mm | Extreme 53 |
| 14 Jan | 34.9 °C | 14 % | 35 km/h | 0.0 mm | Extreme 54 |
| 15 Jan | 34.8 °C | 13 % | 36 km/h | 0.0 mm | Extreme 54 |
| 16 Jan | 35.5 °C | 11 % | 39 km/h | 0.0 mm | Extreme 56 |
| 17 Jan | 35.4 °C | 11 % | 38 km/h | 0.0 mm | Extreme 56 |
| 18 Jan | 35.5 °C | 11 % | 40 km/h | 0.0 mm | Extreme 58 |
| 19 Jan | 36.3 °C | 12 % | 35 km/h | 0.0 mm | Extreme 54 |
| 20 Jan | 37.1 °C | 11 % | 36 km/h | 0.0 mm | Extreme 55 |
| 21 Jan | 37.4 °C | 10 % | 40 km/h | 0.0 mm | Extreme 58 |
| 22 Jan | 36.8 °C | 10 % | 35 km/h | 0.0 mm | Extreme 54 |
| 23 Jan after | 36.2 °C | 9 % | 28 km/h | 0.0 mm | Extreme 54 |
| 24 Jan after | 37.3 °C | 8 % | 36 km/h | 0.0 mm | Extreme 57 |
| 25 Jan after | 35.9 °C | 15 % | 25 km/h | 0.0 mm | Extreme 53 |
| 26 Jan after | 36.7 °C | 14 % | 25 km/h | 0.0 mm | Extreme 55 |
| 27 Jan after | 38.0 °C | 9 % | 34 km/h | 0.0 mm | Extreme 55 |
| 28 Jan after | 37.2 °C | 9 % | 28 km/h | 0.0 mm | Extreme 52 |
| 29 Jan after | 38.0 °C | 8 % | 30 km/h | 0.0 mm | Extreme 54 |
| 30 Jan after | 36.9 °C | 10 % | 22 km/h | 0.0 mm | Very high 50 |
| 31 Jan after | 37.4 °C | 11 % | 26 km/h | 0.0 mm | Very high 50 |
| 1 Feb after | 37.9 °C | 7 % | 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 12 January 2023 the air beside the fire reached 106 µg/m³ of PM2.5. That day averaged 46: 3.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 · 0Every 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 Yalinga fire last?
- GWIS (Copernicus) dates it between 2 January 2023 and 22 January 2023: 21 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 40,751 hectares (407.5 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Yalinga (40,754 ha, 1.0 %); Djema (217 ha, 0.0 %).
- What was the weather like?
- During the fire the temperature reached 37.4 °C, humidity dropped to 10 % and gusts hit 42 km/h. The fire danger index (FWI) reached 58, 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 · 2 Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
- Last day with fire: 25 January 2023 → 22 January 2023.
- Start date: 29 December 2022 → 2 January 2023.
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. No 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.