Skip to content
worldfires
CF · Central African Republic · →

Yalinga fire, 4 February 2022 Yalinga, Djema

Out · last detection 11 Feb 2022, 12:21 UTC

The fire started on 4 February 2022 in Yalinga, Central African Republic, and satellites saw it burning for 8 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 17,142 hectares from heat detections, spread across 2 municipalities.

It is the 77th largest in Haute-Kotto since 2016 (of 372 with a page). Number 21 in Central African Republic in 2022, of 98.

Compare with…
Burnt area
17,142ha
GWIS perimeter (Copernicus)
Duration
8days
4 Feb 2022 – 11 Feb 2022
Municipalities hit
2
sub-prefectures
Started on
4 Feb
2022
Heat detections
551
in a single hotspot: 77 MW
Danger at start
57
Extreme · FWI index
Average daily power
341MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 4 Feb11 Feb
11 Feb 2022

How it evolved, day by day

4 Feb 2022 · 321 MW · 121 5 Feb 2022 · 109 MW · 34 6 Feb 2022 · 560 MW · 164 7 Feb 2022 · 955 MW · 118 8 Feb 2022 · 348 MW · 43 9 Feb 2022 · 429 MW · 69 10 Feb 2022 · 1 MW · 1 11 Feb 2022 · 3 MW · 1
4 Feb 6 Feb 7 Feb 8 Feb 10 Feb

Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.

The weather it burned in

38°high
39km/h · peak gust
7%lowest humidity

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: 13,539 ha in 2016, 7,928 ha in 2017, 10,230 ha in 2018, 6,030 ha in 2019, 23,293 ha in 2020, 4,217 ha in 2021. Part of it burned more than once, so the yearly figures add up to more than the 17,085 ha that had burned before.

How big is it?

10 km
It burned the equivalent of 11% of the area of London (171 km² against 1,583 km²).

London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).

This compares size, not location: both shapes are at the same scale, north up, centred on each other.

What happened to each town

  1. Yalinga where it started
    11,879 ha reached on 4 Feb
    0.3 %
  2. 5,359 ha reached on 4 Feb
    0.2 %

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 2020
Built-up area< 0.1 ha
Residents< 20

Inside 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)
4 Feb 37.3 °C 9 % 37 km/h 0.0 mm Extreme 57
5 Feb 33.3 °C 11 % 36 km/h 0.0 mm Extreme 58
6 Feb 33.1 °C 10 % 39 km/h 0.0 mm Extreme 58
7 Feb 34.2 °C 8 % 38 km/h 0.0 mm Extreme 58
8 Feb 35.9 °C 7 % 37 km/h 0.0 mm Extreme 57
9 Feb 37.0 °C 9 % 28 km/h 0.0 mm Extreme 53
10 Feb 37.5 °C 9 % 38 km/h 0.0 mm Extreme 58
11 Feb 37.1 °C 9 % 39 km/h 0.0 mm Extreme 60
12 Feb after 37.5 °C 9 % 37 km/h 0.0 mm Extreme 59
13 Feb after 37.7 °C 9 % 36 km/h 0.0 mm Extreme 58
14 Feb after 37.9 °C 8 % 39 km/h 0.0 mm Extreme 61
15 Feb after 37.7 °C 6 % 32 km/h 0.0 mm Extreme 56
16 Feb after 36.6 °C 8 % 23 km/h 0.0 mm Extreme 56
17 Feb after 37.5 °C 7 % 22 km/h 0.0 mm Extreme 53
18 Feb after 38.0 °C 6 % 22 km/h 0.0 mm Extreme 54
19 Feb after 37.3 °C 6 % 36 km/h 0.0 mm Extreme 67
20 Feb after 35.4 °C 8 % 36 km/h 0.0 mm Extreme 66
21 Feb after 35.4 °C 8 % 37 km/h 0.0 mm Extreme 63

Before and after, from space

Drag the line to compare the same ground before the fire and after it.

Before · 28 Jan 2022
After · 18 Feb 2022

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 · 551Every satellite heat detection, one by one, with time, satellite, power and coordinates.
⬇ Download CSV Times in UTC. Each detection is a 375 m pixel: a large fire yields hundreds per pass.
Date and timeSatelliteFRP (MW)LatLon

Other fires nearby

All fires in Central African Republic ›

Frequently asked questions

How long did the Yalinga fire last?
GWIS (Copernicus) dates it between 4 February 2022 and 11 February 2022: 8 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 17,142 hectares (171.4 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire entered 2 municipalities: Yalinga (11,879 ha, 0.3 %); Djema (5,359 ha, 0.2 %).
What was the weather like?
During the fire the temperature reached 37.5 °C, humidity dropped to 7 % and gusts hit 39 km/h. The fire danger index (FWI) reached 60, 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.

RSS Changes to this page

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
What do you think is wrong?

We will only use your email to reply about this report. Privacy.

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. 551 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.

How we build fire pages: methodology ›

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.