Skip to content
worldfires
CF · Central African Republic · →

Yalinga fire, 26 December 2017 Yalinga

Out · last detection 1 Jan 2018, 11:44 UTC

The fire started on 26 December 2017 in Yalinga, Central African Republic, and satellites saw it burning for 7 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 6,058 hectares from heat detections, spread across a single municipality.

It is the 281th largest in Haute-Kotto since 2016 (of 372 with a page). Number 72 in Central African Republic in 2017, of 100.

Compare with…
Burnt area
6,058ha
GWIS perimeter (Copernicus)
Duration
7days
26 Dec 2017 – 1 Jan 2018
Municipalities hit
1
sub-prefectures
Started on
26 Dec
2017
Heat detections
152
in a single hotspot: 91 MW
Danger at start
50
Extreme · FWI index
Average daily power
290MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 26 Dec1 Jan
1 Jan 2018

How it evolved, day by day

26 Dec 2017 · 44 MW · 9 27 Dec 2017 · 876 MW · 74 28 Dec 2017 · 617 MW · 41 29 Dec 2017 · 170 MW · 19 31 Dec 2017 · 27 MW · 4 1 Jan 2018 · 6 MW · 5
26 Dec 27 Dec 28 Dec 29 Dec 31 Dec 1 Jan

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

The weather it burned in

36°high
45km/h · peak gust
13%lowest humidity

It had gone 36 days without rain (1 mm or more) when it started.

This area had burned before

56% of the perimeter overlaps earlier fires recorded since 2016: 3,406 ha in 2016.

How big is it?

10 km
It burned the equivalent of 3.8% of the area of London (61 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
    6,100 ha reached on 26 Dec
    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 2015
Built-up area< 0.1 ha
Residents< 20

Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2015, 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)
26 Dec 33.9 °C 16 % 41 km/h 0.0 mm Extreme 50
27 Dec 34.3 °C 16 % 35 km/h 0.0 mm Very high 47
28 Dec 35.8 °C 16 % 29 km/h 0.0 mm Very high 46
29 Dec 35.5 °C 15 % 35 km/h 0.0 mm Very high 47
30 Dec 35.6 °C 13 % 41 km/h 0.0 mm Extreme 52
31 Dec 33.3 °C 15 % 33 km/h 0.0 mm Extreme 51
1 Jan 31.8 °C 16 % 45 km/h 0.0 mm Extreme 53
2 Jan after 30.7 °C 12 % 37 km/h 0.0 mm Extreme 51
3 Jan after 31.0 °C 10 % 38 km/h 0.0 mm Extreme 50
4 Jan after 31.4 °C 11 % 39 km/h 0.0 mm Extreme 51
5 Jan after 31.1 °C 12 % 37 km/h 0.0 mm Extreme 51
6 Jan after 31.7 °C 13 % 34 km/h 0.0 mm Extreme 50
7 Jan after 32.2 °C 12 % 37 km/h 0.0 mm Extreme 52
8 Jan after 32.4 °C 13 % 36 km/h 0.0 mm Extreme 51
9 Jan after 32.1 °C 13 % 39 km/h 0.0 mm Extreme 54
10 Jan after 32.9 °C 14 % 36 km/h 0.0 mm Extreme 52
11 Jan after 33.7 °C 13 % 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.

Before · 19 Dec 2017
After · 8 Jan 2018

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 · 152Every 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?
According to the heat detections seen by satellite inside the perimeter, it burned from 26 December 2017 to 1 January 2018 (7 days). The perimeter dates it from 26 December 2017 to 29 December 2017.
How much area did it burn?
The perimeter GWIS (Copernicus) rebuilt from heat detections is 6,058 hectares (60.6 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Yalinga (6,100 ha, 0.2 %).
What was the weather like?
During the fire the temperature reached 35.8 °C, humidity dropped to 13 % and gusts hit 45 km/h. The fire danger index (FWI) reached 53, 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 adjusted with the VIIRS detections inside the perimeter, which said 26 December 2017 to 29 December 2017. 152 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 2015, 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.