Yalinga fire, March 2024 Yalinga
The fire started on 3 March 2024 in Yalinga, Central African Republic, and satellites saw it burning for 9 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 16,523 hectares from heat detections, spread across a single municipality.
It is the 79th largest in Haute-Kotto since 2016 (of 372 with a page). Number 11 in Central African Republic in 2024, of 91.
Compare with…
- Burnt area
- 16,523ha
- GWIS perimeter (Copernicus)
- Duration
- 9days
- 3 Mar 2024 – 11 Mar 2024
- Municipalities hit
- 1
- sub-prefectures
- Started on
- 3 Mar
- 2024
- Heat detections
- 530
- in a single hotspot: 182 MW
- Danger at start
- 50
- Very high · FWI index
- Average daily power
- 464MW
- 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: 12,086 ha in 2016, 11,108 ha in 2017, 11,402 ha in 2018, 10,396 ha in 2019, 25,050 ha in 2020, 3,304 ha in 2021, 15,468 ha in 2022, 7,958 ha in 2023. Part of it burned more than once, so the yearly figures add up to more than the 16,628 ha that had burned before.
- 13,969 ha Yalinga fire, January 2020 114,388 ha in total; the hectares shown are those it shares with this fire
- 11,554 ha Yalinga fire, January 2022 73,470 ha in total; the hectares shown are those it shares with this fire
- 10,891 ha Yalinga fire, December 2020 979,715 ha in total; the hectares shown are those it shares with this fire
- 10,821 ha Yalinga fire, December 2022 78,074 ha in total; the hectares shown are those it shares with this fire
- 9,328 ha Yalinga fire, January 2018 30,294 ha in total; the hectares shown are those it shares with this fire
- 8,655 ha Yalinga fire, January 2017 45,164 ha in total; the hectares shown are those it shares with this fire
- 7,698 ha Yalinga fire, December 2018 267,715 ha in total; the hectares shown are those it shares with this fire
- 4,733 ha Yalinga fire, January 2016 15,020 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 started16,592 ha reached on 3 Mar0.4 %
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 Mar | 38.2 °C | 21 % | 30 km/h | 0.0 mm | Very high 50 |
| 4 Mar | 38.8 °C | 15 % | 26 km/h | 0.0 mm | Very high 47 |
| 5 Mar | 39.9 °C | 8 % | 26 km/h | 0.0 mm | Extreme 51 |
| 6 Mar | 39.9 °C | 6 % | 28 km/h | 0.0 mm | Extreme 53 |
| 7 Mar | 38.5 °C | 6 % | 34 km/h | 0.0 mm | Extreme 58 |
| 8 Mar | 39.1 °C | 9 % | 29 km/h | 0.0 mm | Extreme 60 |
| 9 Mar | 39.7 °C | 9 % | 24 km/h | 0.0 mm | Extreme 52 |
| 10 Mar | 39.3 °C | 13 % | 33 km/h | 0.0 mm | Extreme 56 |
| 11 Mar | 38.2 °C | 17 % | 36 km/h | 0.0 mm | Extreme 56 |
| 12 Mar after | 38.9 °C | 20 % | 30 km/h | 0.0 mm | Very high 50 |
| 13 Mar after | 39.1 °C | 21 % | 35 km/h | 0.9 mm | Very high 43 |
| 14 Mar after | 37.9 °C | 25 % | 26 km/h | 0.3 mm | Very high 44 |
| 15 Mar after | 35.9 °C | 28 % | 32 km/h | 0.0 mm | Very high 43 |
| 16 Mar after | 34.9 °C | 32 % | 31 km/h | 0.5 mm | Very high 39 |
| 17 Mar after | 37.9 °C | 23 % | 30 km/h | 0.0 mm | Very high 40 |
| 18 Mar after | 37.4 °C | 27 % | 32 km/h | 0.8 mm | Very high 39 |
| 19 Mar after | 35.4 °C | 29 % | 24 km/h | 0.4 mm | High 35 |
| 20 Mar after | 35.6 °C | 18 % | 21 km/h | 0.0 mm | Very high 41 |
| 21 Mar after | 39.1 °C | 14 % | 32 km/h | 0.0 mm | Very high 49 |
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 10 March 2024 the air beside the fire reached 106 µg/m³ of PM2.5. That day averaged 73: 4.9 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 · 530Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 73,470 haYalinga14 January 2022 · 22 days · 4 km away
- 114,388 haYalinga18 January 2020 · 39 days · 14 km away
- 78,074 haYalinga28 December 2022 · 32 days · 17 km away
- 149,622 haYalinga15 February 2026 · 31 days · 23 km away
- 131,336 haRafaï4 January 2020 · 38 days · 37 km away
- 125,550 haRafaï2 January 2016 · 31 days · 39 km away
Frequently asked questions
- How long did the Yalinga fire last?
- GWIS (Copernicus) dates it between 3 March 2024 and 11 March 2024: 9 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 16,523 hectares (165.2 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Yalinga (16,592 ha, 0.4 %).
- What was the weather like?
- During the fire the temperature reached 39.9 °C, humidity dropped to 6 % and gusts hit 36 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.
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 from the perimeter: the VIIRS detections inside it did not change them. 530 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.