Yalinga fire, 3 January 2022 Yalinga
The fire started on 3 January 2022 in Yalinga, Central African Republic, and satellites saw it burning for 33 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 87,524 hectares from heat detections, spread across a single municipality.
It is the 19th largest in Haute-Kotto since 2016 (of 372 with a page). Number 5 in Central African Republic in 2022, of 97.
Compare with…
- Burnt area
- 87,524ha
- GWIS perimeter (Copernicus)
- Duration
- 33days
- 3 Jan 2022 – 4 Feb 2022
- Municipalities hit
- 1
- sub-prefectures
- Started on
- 3 Jan
- 2022
- Heat detections
- 3,697
- in a single hotspot: 163 MW
- Danger at start
- 47
- Very high · FWI index
- Average daily power
- 787MW
- 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 53 days without rain (1 mm or more) when it started.
This area had burned before
70% of the perimeter overlaps earlier fires recorded since 2016: 39,823 ha in 2016, 43,825 ha in 2017, 51,848 ha in 2018, 10,890 ha in 2019, 106,383 ha in 2020, 9,960 ha in 2021. Part of it burned more than once, so the yearly figures add up to more than the 60,933 ha that had burned before.
- 52,628 ha Yalinga fire, January 2020 353,408 ha in total; the hectares shown are those it shares with this fire
- 30,060 ha Yalinga fire, December 2018 136,358 ha in total; the hectares shown are those it shares with this fire
- 28,795 ha Yalinga fire, December 2020 261,604 ha in total; the hectares shown are those it shares with this fire
- 13,666 ha Yalinga fire, December 2017 26,411 ha in total; the hectares shown are those it shares with this fire
- 11,616 ha Yalinga fire, December 2016 14,157 ha in total; the hectares shown are those it shares with this fire
- 10,181 ha Yalinga fire, December 2018 71,520 ha in total; the hectares shown are those it shares with this fire
- 8,819 ha Yalinga fire, December 2018 109,809 ha in total; the hectares shown are those it shares with this fire
- 7,393 ha Yalinga fire, December 2020 9,377 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 started88,076 ha reached on 3 Jan2.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 Jan | 33.2 °C | 15 % | 34 km/h | 0.0 mm | Very high 47 |
| 6 Jan | 34.5 °C | 13 % | 31 km/h | 0.0 mm | Very high 45 |
| 7 Jan | 35.8 °C | 14 % | 36 km/h | 0.0 mm | Very high 47 |
| 8 Jan | 36.3 °C | 15 % | 37 km/h | 0.0 mm | Very high 48 |
| 9 Jan | 37.0 °C | 13 % | 38 km/h | 0.0 mm | Extreme 51 |
| 10 Jan | 37.1 °C | 14 % | 25 km/h | 0.0 mm | Very high 43 |
| 11 Jan | 36.1 °C | 15 % | 36 km/h | 0.0 mm | Extreme 50 |
| 12 Jan | 37.0 °C | 16 % | 34 km/h | 0.0 mm | Very high 48 |
| 13 Jan | 35.5 °C | 19 % | 24 km/h | 0.0 mm | Very high 42 |
| 14 Jan | 35.5 °C | 21 % | 37 km/h | 0.0 mm | Very high 49 |
| 15 Jan | 36.4 °C | 19 % | 21 km/h | 0.0 mm | Very high 43 |
| 16 Jan | 35.3 °C | 19 % | 26 km/h | 0.0 mm | Very high 45 |
| 17 Jan | 35.0 °C | 10 % | 31 km/h | 0.0 mm | Very high 49 |
| 18 Jan | 33.7 °C | 17 % | 37 km/h | 0.0 mm | Extreme 52 |
| 19 Jan | 33.3 °C | 14 % | 37 km/h | 0.0 mm | Extreme 54 |
| 20 Jan | 33.1 °C | 12 % | 39 km/h | 0.0 mm | Extreme 54 |
| 21 Jan | 33.1 °C | 11 % | 39 km/h | 0.0 mm | Extreme 54 |
| 22 Jan | 34.4 °C | 11 % | 34 km/h | 0.0 mm | Extreme 51 |
| 23 Jan | 35.3 °C | 12 % | 32 km/h | 0.0 mm | Extreme 50 |
| 24 Jan | 35.8 °C | 12 % | 37 km/h | 0.0 mm | Extreme 53 |
| 25 Jan | 35.9 °C | 11 % | 42 km/h | 0.0 mm | Extreme 57 |
| 26 Jan | 35.6 °C | 12 % | 41 km/h | 0.0 mm | Extreme 57 |
| 27 Jan | 33.9 °C | 11 % | 46 km/h | 0.0 mm | Extreme 62 |
| 28 Jan | 33.6 °C | 11 % | 42 km/h | 0.0 mm | Extreme 59 |
| 29 Jan | 33.4 °C | 9 % | 38 km/h | 0.0 mm | Extreme 56 |
| 30 Jan | 33.9 °C | 9 % | 37 km/h | 0.0 mm | Extreme 56 |
| 31 Jan | 34.4 °C | 8 % | 37 km/h | 0.0 mm | Extreme 56 |
| 1 Feb | 33.7 °C | 10 % | 35 km/h | 0.0 mm | Extreme 55 |
| 2 Feb | 34.3 °C | 11 % | 27 km/h | 0.0 mm | Extreme 51 |
| 3 Feb | 37.4 °C | 10 % | 32 km/h | 0.0 mm | Extreme 54 |
| 4 Feb | 36.4 °C | 8 % | 40 km/h | 0.0 mm | Extreme 60 |
| 5 Feb after | 32.0 °C | 10 % | 36 km/h | 0.0 mm | Extreme 60 |
| 6 Feb after | 32.6 °C | 10 % | 38 km/h | 0.0 mm | Extreme 59 |
| 7 Feb after | 33.3 °C | 8 % | 39 km/h | 0.0 mm | Extreme 60 |
| 8 Feb after | 34.9 °C | 7 % | 37 km/h | 0.0 mm | Extreme 58 |
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 · 3,697Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 108,015 haYalinga24 December 2022 · 36 days · 13 km away
- 979,715 haYalinga24 December 2020 · 76 days · 19 km away
- 87,474 haYalinga25 January 2026 · 44 days · 22 km away
- 109,809 haYalinga16 December 2018 · 48 days · 29 km away
- 140,621 haYalinga19 January 2022 · 25 days · 31 km away
- 353,408 haYalinga1 January 2020 · 52 days · 34 km away
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 2022 to 4 February 2022 (33 days). The perimeter dates it from 5 January 2022 to 29 January 2022.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 87,524 hectares (875.2 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Yalinga (88,076 ha, 2.1 %).
- What was the weather like?
- During the fire the temperature reached 37.1 °C, humidity dropped to 9 % and gusts hit 46 km/h. The fire danger index (FWI) reached 62, 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 January 2022 to 29 January 2022. 3,697 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.