Yalinga fire, 24 January 2022 Yalinga
The fire started on 24 January 2022 in Yalinga, Central African Republic, and satellites saw it burning for 32 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 70,767 hectares from heat detections, spread across a single municipality.
It is the 26th largest in Haute-Kotto since 2016 (of 372 with a page). Number 9 in Central African Republic in 2022, of 97.
Compare with…
- Burnt area
- 70,767ha
- GWIS perimeter (Copernicus)
- Duration
- 32days
- 24 Jan 2022 – 24 Feb 2022
- Municipalities hit
- 1
- sub-prefectures
- Started on
- 24 Jan
- 2022
- Heat detections
- 2,684
- in a single hotspot: 224 MW
- Danger at start
- 49
- Very high · FWI index
- Average daily power
- 610MW
- 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: 47,413 ha in 2016, 7,035 ha in 2017, 51,674 ha in 2018, 12,043 ha in 2019, 36,571 ha in 2020, 33,466 ha in 2021. Part of it burned more than once, so the yearly figures add up to more than the 67,301 ha that had burned before.
- 21,258 ha Yalinga fire, December 2020 979,715 ha in total; the hectares shown are those it shares with this fire
- 19,252 ha Yalinga fire, December 2018 33,071 ha in total; the hectares shown are those it shares with this fire
- 18,488 ha Yalinga fire, January 2020 24,730 ha in total; the hectares shown are those it shares with this fire
- 16,065 ha Yalinga fire, January 2018 23,659 ha in total; the hectares shown are those it shares with this fire
- 10,817 ha Yalinga fire, December 2016 21,676 ha in total; the hectares shown are those it shares with this fire
- 8,473 ha Yalinga fire, January 2016 14,531 ha in total; the hectares shown are those it shares with this fire
- 7,292 ha Yalinga fire, January 2020 353,408 ha in total; the hectares shown are those it shares with this fire
- 6,649 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 started71,143 ha reached on 24 Jan1.7 %
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) |
|---|---|---|---|---|---|
| 24 Jan | 36.1 °C | 13 % | 27 km/h | 0.0 mm | Very high 49 |
| 25 Jan | 36.7 °C | 11 % | 39 km/h | 0.0 mm | Extreme 53 |
| 26 Jan | 36.4 °C | 11 % | 41 km/h | 0.0 mm | Extreme 55 |
| 27 Jan | 35.2 °C | 11 % | 46 km/h | 0.0 mm | Extreme 60 |
| 28 Jan | 34.9 °C | 11 % | 42 km/h | 0.0 mm | Extreme 57 |
| 29 Jan | 34.2 °C | 10 % | 41 km/h | 0.0 mm | Extreme 57 |
| 30 Jan | 34.5 °C | 9 % | 37 km/h | 0.0 mm | Extreme 55 |
| 31 Jan | 35.1 °C | 8 % | 38 km/h | 0.0 mm | Extreme 55 |
| 1 Feb | 34.1 °C | 10 % | 32 km/h | 0.0 mm | Extreme 53 |
| 2 Feb | 35.1 °C | 12 % | 26 km/h | 0.0 mm | Very high 49 |
| 3 Feb | 37.3 °C | 11 % | 31 km/h | 0.0 mm | Extreme 51 |
| 4 Feb | 36.8 °C | 9 % | 38 km/h | 0.0 mm | Extreme 58 |
| 5 Feb | 33.5 °C | 11 % | 38 km/h | 0.0 mm | Extreme 58 |
| 6 Feb | 33.6 °C | 10 % | 39 km/h | 0.0 mm | Extreme 58 |
| 7 Feb | 34.3 °C | 8 % | 39 km/h | 0.0 mm | Extreme 59 |
| 8 Feb | 35.8 °C | 7 % | 38 km/h | 0.0 mm | Extreme 58 |
| 9 Feb | 36.4 °C | 8 % | 31 km/h | 0.0 mm | Extreme 53 |
| 10 Feb | 37.1 °C | 9 % | 35 km/h | 0.0 mm | Extreme 57 |
| 11 Feb | 36.7 °C | 9 % | 39 km/h | 0.0 mm | Extreme 60 |
| 12 Feb | 36.7 °C | 10 % | 35 km/h | 0.0 mm | Extreme 58 |
| 13 Feb | 37.5 °C | 8 % | 34 km/h | 0.0 mm | Extreme 57 |
| 14 Feb | 37.6 °C | 8 % | 38 km/h | 0.0 mm | Extreme 60 |
| 15 Feb | 37.4 °C | 6 % | 30 km/h | 0.0 mm | Extreme 57 |
| 16 Feb | 36.0 °C | 8 % | 24 km/h | 0.0 mm | Extreme 57 |
| 17 Feb | 37.1 °C | 9 % | 23 km/h | 0.0 mm | Extreme 55 |
| 18 Feb | 37.7 °C | 6 % | 24 km/h | 0.0 mm | Extreme 53 |
| 19 Feb | 37.2 °C | 7 % | 42 km/h | 0.0 mm | Extreme 64 |
| 20 Feb | 35.1 °C | 8 % | 36 km/h | 0.0 mm | Extreme 65 |
| 21 Feb | 33.9 °C | 9 % | 30 km/h | 0.0 mm | Extreme 60 |
| 22 Feb | 36.6 °C | 7 % | 28 km/h | 0.0 mm | Extreme 55 |
| 23 Feb | 37.3 °C | 7 % | 24 km/h | 0.0 mm | Extreme 54 |
| 24 Feb | 37.8 °C | 8 % | 25 km/h | 0.0 mm | Extreme 53 |
| 25 Feb after | 37.5 °C | 6 % | 40 km/h | 0.0 mm | Extreme 63 |
| 26 Feb after | 37.0 °C | 8 % | 40 km/h | 0.0 mm | Extreme 66 |
| 27 Feb after | 38.0 °C | 8 % | 39 km/h | 0.0 mm | Extreme 63 |
| 28 Feb after | 38.5 °C | 8 % | 41 km/h | 0.0 mm | Extreme 65 |
| 1 Mar after | 37.8 °C | 7 % | 39 km/h | 0.0 mm | Extreme 66 |
| 2 Mar after | 38.1 °C | 9 % | 26 km/h | 0.0 mm | Extreme 58 |
| 3 Mar after | 35.8 °C | 18 % | 45 km/h | 0.0 mm | Extreme 59 |
| 4 Mar after | 37.1 °C | 22 % | 37 km/h | 0.8 mm | Very high 39 |
| 5 Mar after | 38.8 °C | 14 % | 29 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.
Detections table · 2,684Every 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 24 January 2022 to 24 February 2022 (32 days). The perimeter dates it from 24 January 2022 to 23 February 2022.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 70,767 hectares (707.7 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Yalinga (71,143 ha, 1.7 %).
- What was the weather like?
- During the fire the temperature reached 37.7 °C, humidity dropped to 6 % and gusts hit 46 km/h. The fire danger index (FWI) reached 65, 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 24 January 2022 to 23 February 2022. 2,684 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.