Yalinga fire, 11 January 2026 Yalinga
The fire started on 11 January 2026 in Yalinga, Central African Republic, and satellites saw it burning for 23 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 35,430 hectares from heat detections, spread across a single municipality.
It is the 46th largest in Haute-Kotto since 2016 (of 373 with a page). Number 13 in Central African Republic in 2026, of 161.
Compare with…
- Burnt area
- 35,430ha
- GWIS perimeter (Copernicus)
- Duration
- 23days
- 11 Jan 2026 – 2 Feb 2026
- Municipalities hit
- 1
- sub-prefectures
- Started on
- 11 Jan
- 2026
- Heat detections
- 721
- in a single hotspot: 56 MW
- Danger at start
- 48
- Very high · FWI index
- Average daily power
- 273MW
- 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
100% of the perimeter overlaps earlier fires recorded since 2016: 30,999 ha in 2016, 5,613 ha in 2017, 28,955 ha in 2018, 4,020 ha in 2019, 19,439 ha in 2020, 22,064 ha in 2021, 33,528 ha in 2022, 14,638 ha in 2023, 11,524 ha in 2024, 7,692 ha in 2025. Part of it burned more than once, so the yearly figures add up to more than the 35,618 ha that had burned before.
- 21,382 ha Yalinga fire, December 2022 51,515 ha in total; the hectares shown are those it shares with this fire
- 18,094 ha Yalinga fire, January 2022 70,767 ha in total; the hectares shown are those it shares with this fire
- 17,242 ha Yalinga fire, December 2020 979,715 ha in total; the hectares shown are those it shares with this fire
- 12,314 ha Yalinga fire, December 2016 21,676 ha in total; the hectares shown are those it shares with this fire
- 10,524 ha Yalinga fire, December 2018 33,071 ha in total; the hectares shown are those it shares with this fire
- 10,073 ha Yalinga fire, January 2020 24,730 ha in total; the hectares shown are those it shares with this fire
- 7,935 ha Yalinga fire, January 2016 14,531 ha in total; the hectares shown are those it shares with this fire
- 6,998 ha Yalinga fire, December 2018 45,359 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 started35,621 ha reached on 11 Jan0.9 %
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) |
|---|---|---|---|---|---|
| 11 Jan | 34.6 °C | 16 % | 32 km/h | 0.0 mm | Very high 48 |
| 12 Jan | 34.6 °C | 16 % | 29 km/h | 0.0 mm | Very high 47 |
| 13 Jan | 35.4 °C | 15 % | 40 km/h | 0.0 mm | Extreme 53 |
| 14 Jan | 34.4 °C | 15 % | 43 km/h | 0.0 mm | Extreme 57 |
| 15 Jan | 34.5 °C | 14 % | 41 km/h | 0.0 mm | Extreme 56 |
| 16 Jan | 34.4 °C | 15 % | 40 km/h | 0.0 mm | Extreme 54 |
| 17 Jan | 34.6 °C | 13 % | 32 km/h | 0.0 mm | Extreme 51 |
| 18 Jan | 35.4 °C | 12 % | 35 km/h | 0.0 mm | Extreme 52 |
| 19 Jan | 35.8 °C | 13 % | 35 km/h | 0.0 mm | Extreme 52 |
| 20 Jan | 36.0 °C | 14 % | 34 km/h | 0.0 mm | Extreme 52 |
| 21 Jan | 36.4 °C | 16 % | 34 km/h | 0.0 mm | Extreme 53 |
| 22 Jan | 36.2 °C | 18 % | 20 km/h | 0.0 mm | Very high 49 |
| 23 Jan | 35.3 °C | 22 % | 24 km/h | 0.0 mm | Very high 46 |
| 24 Jan | 36.9 °C | 18 % | 31 km/h | 0.0 mm | Very high 47 |
| 25 Jan | 37.8 °C | 12 % | 37 km/h | 0.0 mm | Extreme 53 |
| 26 Jan | 37.9 °C | 10 % | 39 km/h | 0.0 mm | Extreme 56 |
| 27 Jan | 37.1 °C | 12 % | 27 km/h | 0.0 mm | Very high 50 |
| 28 Jan | 35.4 °C | 13 % | 31 km/h | 0.0 mm | Extreme 52 |
| 29 Jan | 35.8 °C | 11 % | 37 km/h | 0.0 mm | Extreme 56 |
| 30 Jan | 36.7 °C | 11 % | 35 km/h | 0.0 mm | Extreme 55 |
| 31 Jan | 35.6 °C | 12 % | 22 km/h | 0.0 mm | Extreme 54 |
| 1 Feb | 34.7 °C | 19 % | 25 km/h | 0.0 mm | Very high 46 |
| 2 Feb | 36.0 °C | 16 % | 26 km/h | 0.0 mm | Very high 46 |
| 3 Feb after | 37.0 °C | 13 % | 34 km/h | 0.0 mm | Extreme 52 |
| 4 Feb after | 37.3 °C | 11 % | 45 km/h | 0.0 mm | Extreme 60 |
| 5 Feb after | 38.1 °C | 12 % | 35 km/h | 0.0 mm | Extreme 53 |
| 6 Feb after | 34.2 °C | 24 % | 26 km/h | 0.0 mm | Very high 46 |
| 7 Feb after | 35.8 °C | 16 % | 19 km/h | 0.0 mm | Very high 44 |
| 8 Feb after | 36.3 °C | 9 % | 36 km/h | 0.0 mm | Extreme 54 |
| 9 Feb after | 34.3 °C | 23 % | 28 km/h | 0.0 mm | Very high 45 |
| 10 Feb after | 34.8 °C | 21 % | 30 km/h | 0.0 mm | Very high 46 |
| 11 Feb after | 36.1 °C | 19 % | 34 km/h | 0.0 mm | Very high 47 |
| 12 Feb after | 35.9 °C | 19 % | 26 km/h | 0.0 mm | Very high 47 |
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 19 January 2026 the air beside the fire reached 68 µg/m³ of PM2.5. That day averaged 44: 3.0 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 · 721Every 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 11 January 2026 to 2 February 2026 (23 days). The perimeter dates it from 16 January 2026 to 26 January 2026.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 35,430 hectares (354.3 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Yalinga (35,621 ha, 0.9 %).
- What was the weather like?
- During the fire the temperature reached 37.9 °C, humidity dropped to 10 % and gusts hit 43 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; 2 polygons grouped in this page.
- Dates adjusted with the VIIRS detections inside the perimeter, which said 16 January 2026 to 26 January 2026. 721 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.