Yalinga fire, 8 January 2018 Yalinga
The fire started on 8 January 2018 in Yalinga, Central African Republic, and satellites saw it burning for 27 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 37,364 hectares from heat detections, spread across a single municipality.
It is the 45th largest in Haute-Kotto since 2016 (of 372 with a page). Number 12 in Central African Republic in 2018, of 81.
- Burnt area
- 37,364ha
- GWIS perimeter (Copernicus)
- Duration
- 27days
- 8 Jan 2018 – 3 Feb 2018
- Municipalities hit
- 1
- sub-prefectures
- Started on
- 8 Jan
- 2018
- Heat detections
- 2,028
- in a single hotspot: 164 MW
- Danger at start
- 48
- Very high · FWI index
- Energy released
- 15.5GW
- sum of detected power
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 49 days without rain (1 mm or more) when it started. Rain came after the fire: 2.0 mm on 12 Feb.
This area had burned before
81% of the perimeter overlaps earlier fires recorded since 2016: 33,850 ha in 2016, 11,607 ha in 2017. Part of it burned more than once, so the yearly figures add up to more than the 30,228 ha that had burned before.
- 10,630 ha Yalinga fire, December 2016 26,580 ha in total; the hectares shown are those it shares with this fire
- 9,072 ha Yalinga fire, January 2017 238,204 ha in total; the hectares shown are those it shares with this fire
- 8,493 ha Yalinga fire, January 2016 15,214 ha in total; the hectares shown are those it shares with this fire
- 6,060 ha Rafaï fire, January 2016 125,550 ha in total; the hectares shown are those it shares with this fire
What happened to each town
-
Yalinga where it started37,532 ha reached on 8 Jan0.9 %
Burnt area inside each municipality, from crossing the GWIS perimeter with administrative boundaries. The distance is from the town centre to the nearest fire: staying a kilometre away does not mean it reached the houses.
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) |
|---|---|---|---|---|---|
| 8 Jan | 33.8 °C | 13 % | 34 km/h | 0.0 mm | Very high 48 |
| 9 Jan | 33.5 °C | 13 % | 37 km/h | 0.0 mm | Extreme 50 |
| 10 Jan | 34.5 °C | 13 % | 36 km/h | 0.0 mm | Extreme 50 |
| 11 Jan | 34.9 °C | 14 % | 33 km/h | 0.0 mm | Very high 48 |
| 12 Jan | 35.8 °C | 14 % | 34 km/h | 0.0 mm | Very high 49 |
| 13 Jan | 36.8 °C | 13 % | 30 km/h | 0.0 mm | Very high 47 |
| 14 Jan | 35.9 °C | 13 % | 27 km/h | 0.0 mm | Very high 45 |
| 15 Jan | 34.9 °C | 14 % | 39 km/h | 0.0 mm | Extreme 54 |
| 16 Jan | 35.1 °C | 12 % | 37 km/h | 0.0 mm | Extreme 54 |
| 17 Jan | 35.4 °C | 10 % | 38 km/h | 0.0 mm | Extreme 55 |
| 18 Jan | 35.2 °C | 12 % | 32 km/h | 0.0 mm | Extreme 51 |
| 19 Jan | 35.3 °C | 12 % | 31 km/h | 0.0 mm | Extreme 51 |
| 20 Jan | 35.4 °C | 12 % | 38 km/h | 0.0 mm | Extreme 56 |
| 21 Jan | 35.8 °C | 11 % | 32 km/h | 0.0 mm | Extreme 52 |
| 22 Jan | 36.8 °C | 11 % | 36 km/h | 0.0 mm | Extreme 54 |
| 23 Jan | 36.1 °C | 11 % | 34 km/h | 0.0 mm | Extreme 56 |
| 24 Jan | 34.9 °C | 10 % | 22 km/h | 0.0 mm | Very high 49 |
| 25 Jan | 35.0 °C | 14 % | 23 km/h | 0.0 mm | Very high 48 |
| 26 Jan | 34.7 °C | 12 % | 28 km/h | 0.0 mm | Extreme 53 |
| 27 Jan | 35.5 °C | 13 % | 44 km/h | 0.0 mm | Extreme 60 |
| 28 Jan | 35.9 °C | 11 % | 42 km/h | 0.0 mm | Extreme 61 |
| 29 Jan | 35.8 °C | 10 % | 41 km/h | 0.0 mm | Extreme 60 |
| 30 Jan | 35.5 °C | 11 % | 43 km/h | 0.0 mm | Extreme 62 |
| 31 Jan | 35.2 °C | 11 % | 44 km/h | 0.0 mm | Extreme 63 |
| 1 Feb | 35.8 °C | 11 % | 44 km/h | 0.0 mm | Extreme 63 |
| 2 Feb | 36.8 °C | 10 % | 43 km/h | 0.0 mm | Extreme 63 |
| 3 Feb | 37.4 °C | 13 % | 43 km/h | 0.0 mm | Extreme 64 |
| 4 Feb after | 37.2 °C | 13 % | 42 km/h | 0.0 mm | Extreme 61 |
| 5 Feb after | 38.3 °C | 11 % | 34 km/h | 0.0 mm | Extreme 57 |
| 6 Feb after | 39.4 °C | 11 % | 41 km/h | 0.0 mm | Extreme 61 |
| 7 Feb after | 40.1 °C | 10 % | 41 km/h | 0.0 mm | Extreme 63 |
| 8 Feb after | 40.4 °C | 10 % | 33 km/h | 0.0 mm | Extreme 56 |
| 9 Feb after | 39.3 °C | 13 % | 22 km/h | 0.0 mm | Extreme 50 |
| 10 Feb after | 37.5 °C | 16 % | 35 km/h | 0.0 mm | Extreme 59 |
| 11 Feb after | 36.8 °C | 20 % | 36 km/h | 0.0 mm | Extreme 53 |
| 12 Feb after | 36.4 °C | 30 % | 33 km/h | 2.0 mm | High 25 |
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,028Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 78,074 haYalinga28 December 2022 · 32 days · 7 km away
- 149,622 haYalinga15 February 2026 · 31 days · 10 km away
- 73,470 haYalinga14 January 2022 · 22 days · 21 km away
- 114,388 haYalinga18 January 2020 · 39 days · 28 km away
- 238,204 haYalinga17 January 2017 · 22 days · 33 km away
- 70,767 haYalinga24 January 2022 · 32 days · 39 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 8 January 2018 to 3 February 2018 (27 days). The perimeter dates it from 8 January 2018 to 1 February 2018.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 37,364 hectares (373.6 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Yalinga (37,532 ha, 0.9 %).
- What was the weather like?
- During the fire the temperature reached 37.4 °C, humidity dropped to 10 % and gusts hit 44 km/h. The fire danger index (FWI) reached 64, 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
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
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.