Yalinga fire, 3 January 2026 Yalinga, Djema
The fire started on 3 January 2026 in Yalinga, Central African Republic, and satellites saw it burning for 29 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 33,341 hectares from heat detections, spread across 2 municipalities.
It is the 50th largest in Haute-Kotto since 2016 (of 372 with a page). Number 12 in Central African Republic in 2026, of 147.
Compare with…
- Burnt area
- 33,341ha
- GWIS perimeter (Copernicus)
- Duration
- 29days
- 3 Jan 2026 – 31 Jan 2026
- Municipalities hit
- 2
- sub-prefectures
- Started on
- 3 Jan
- 2026
- Heat detections
- 747
- in a single hotspot: 68 MW
- Danger at start
- 50
- Very high · FWI index
- Average daily power
- 185MW
- 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
95% of the perimeter overlaps earlier fires recorded since 2016: 3,901 ha in 2016, 16,082 ha in 2017, 9,993 ha in 2018, 7,457 ha in 2019, 13,479 ha in 2020, 7,782 ha in 2021, 13,116 ha in 2022, 1,365 ha in 2023, 4,615 ha in 2024, 14,291 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 31,718 ha that had burned before.
- 7,984 ha Yalinga fire, December 2022 10,102 ha in total; the hectares shown are those it shares with this fire
- 4,580 ha Yalinga fire, December 2017 5,832 ha in total; the hectares shown are those it shares with this fire
- 4,395 ha Yalinga fire, December 2020 261,604 ha in total; the hectares shown are those it shares with this fire
- 3,510 ha Yalinga fire, January 2025 5,036 ha in total; the hectares shown are those it shares with this fire
- 3,237 ha Yalinga fire, January 2025 20,597 ha in total; the hectares shown are those it shares with this fire
- 2,951 ha Yalinga fire, December 2020 11,022 ha in total; the hectares shown are those it shares with this fire
- 2,741 ha Yalinga fire, January 2020 5,798 ha in total; the hectares shown are those it shares with this fire
- 1,161 ha Yalinga fire, December 2018 5,406 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 started33,199 ha reached on 3 Jan0.8 %
-
350 ha reached on 5 Jan0.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 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) |
|---|---|---|---|---|---|
| 3 Jan | 35.8 °C | 17 % | 34 km/h | 0.0 mm | Very high 50 |
| 4 Jan | 35.7 °C | 12 % | 38 km/h | 0.0 mm | Extreme 53 |
| 5 Jan | 35.5 °C | 13 % | 37 km/h | 0.0 mm | Extreme 53 |
| 6 Jan | 35.1 °C | 12 % | 36 km/h | 0.0 mm | Extreme 53 |
| 7 Jan | 35.0 °C | 14 % | 37 km/h | 0.0 mm | Extreme 53 |
| 8 Jan | 35.9 °C | 13 % | 36 km/h | 0.0 mm | Extreme 53 |
| 9 Jan | 35.7 °C | 16 % | 40 km/h | 0.0 mm | Extreme 55 |
| 10 Jan | 34.0 °C | 18 % | 36 km/h | 0.0 mm | Extreme 52 |
| 11 Jan | 34.7 °C | 16 % | 34 km/h | 0.0 mm | Extreme 51 |
| 12 Jan | 35.1 °C | 14 % | 34 km/h | 0.0 mm | Very high 49 |
| 13 Jan | 34.8 °C | 15 % | 44 km/h | 0.0 mm | Extreme 56 |
| 14 Jan | 33.8 °C | 16 % | 43 km/h | 0.0 mm | Extreme 57 |
| 15 Jan | 33.8 °C | 14 % | 40 km/h | 0.0 mm | Extreme 56 |
| 16 Jan | 33.6 °C | 17 % | 37 km/h | 0.0 mm | Extreme 53 |
| 17 Jan | 35.0 °C | 13 % | 31 km/h | 0.0 mm | Very high 50 |
| 18 Jan | 35.3 °C | 11 % | 32 km/h | 0.0 mm | Very high 50 |
| 19 Jan | 35.7 °C | 13 % | 38 km/h | 0.0 mm | Extreme 53 |
| 20 Jan | 35.9 °C | 14 % | 35 km/h | 0.0 mm | Extreme 51 |
| 21 Jan | 36.9 °C | 15 % | 37 km/h | 0.0 mm | Extreme 53 |
| 22 Jan | 36.8 °C | 16 % | 24 km/h | 0.0 mm | Very high 49 |
| 23 Jan | 36.2 °C | 19 % | 25 km/h | 0.0 mm | Very high 45 |
| 24 Jan | 37.5 °C | 16 % | 32 km/h | 0.0 mm | Extreme 50 |
| 25 Jan | 37.5 °C | 12 % | 42 km/h | 0.0 mm | Extreme 57 |
| 26 Jan | 37.7 °C | 11 % | 36 km/h | 0.0 mm | Extreme 54 |
| 27 Jan | 37.4 °C | 12 % | 35 km/h | 0.0 mm | Extreme 53 |
| 28 Jan | 36.2 °C | 13 % | 33 km/h | 0.0 mm | Extreme 53 |
| 29 Jan | 35.4 °C | 12 % | 37 km/h | 0.0 mm | Extreme 56 |
| 30 Jan | 36.4 °C | 11 % | 31 km/h | 0.0 mm | Extreme 53 |
| 31 Jan | 36.6 °C | 12 % | 32 km/h | 0.0 mm | Extreme 53 |
| 1 Feb after | 34.9 °C | 15 % | 24 km/h | 0.0 mm | Very high 47 |
| 2 Feb after | 36.5 °C | 11 % | 26 km/h | 0.0 mm | Very high 48 |
| 3 Feb after | 37.0 °C | 13 % | 37 km/h | 0.0 mm | Extreme 56 |
| 4 Feb after | 36.9 °C | 11 % | 46 km/h | 0.0 mm | Extreme 62 |
| 5 Feb after | 37.8 °C | 12 % | 38 km/h | 0.0 mm | Extreme 58 |
| 6 Feb after | 34.7 °C | 22 % | 23 km/h | 0.0 mm | Very high 43 |
| 7 Feb after | 36.9 °C | 10 % | 24 km/h | 0.0 mm | Extreme 54 |
| 8 Feb after | 36.4 °C | 9 % | 36 km/h | 0.0 mm | Extreme 54 |
| 9 Feb after | 35.1 °C | 17 % | 26 km/h | 0.0 mm | Very high 48 |
| 10 Feb after | 35.3 °C | 17 % | 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.
The smoke
CAMS · CopernicusOn 11 January 2026 the air beside the fire reached 75 µg/m³ of PM2.5. That day averaged 55: 3.7 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 · 747Every 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?
- According to the heat detections seen by satellite inside the perimeter, it burned from 3 January 2026 to 31 January 2026 (29 days). The perimeter dates it from 9 January 2026 to 24 January 2026.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 33,341 hectares (333.4 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire entered 2 municipalities: Yalinga (33,199 ha, 0.8 %); Djema (350 ha, 0.0 %).
- What was the weather like?
- During the fire the temperature reached 37.7 °C, humidity dropped to 11 % and gusts hit 44 km/h. The fire danger index (FWI) reached 57, 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 9 January 2026 to 24 January 2026. 747 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.