Skip to content
worldfires
CF · Central African Republic · →

Yalinga fire, 14 December 2016 Yalinga

Out · last detection 23 Dec 2016, 11:57 UTC

The fire started on 14 December 2016 in Yalinga, Central African Republic, and satellites saw it burning for 9 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 5,564 hectares from heat detections, spread across a single municipality.

It is the 317th largest in Haute-Kotto since 2016 (of 372 with a page). Number 137 in Central African Republic in 2016, of 165.

Compare with…
Burnt area
5,564ha
GWIS perimeter (Copernicus)
Duration
9days
14 Dec 2016 – 22 Dec 2016
Municipalities hit
1
sub-prefectures
Started on
14 Dec
2016
Heat detections
160
in a single hotspot: 53 MW
Danger at start
53
Extreme · FWI index
Average daily power
178MW
detected power per day, on average

Where it burned

HOTSPOTS BY DAY 14 Dec22 Dec
23 Dec 2016

How it evolved, day by day

16 Dec 2016 · 204 MW · 16 17 Dec 2016 · 595 MW · 44 18 Dec 2016 · 361 MW · 53 19 Dec 2016 · 193 MW · 24 20 Dec 2016 · 46 MW · 18 21 Dec 2016 · 8 MW · 2 22 Dec 2016 · 11 MW · 2 23 Dec 2016 · 2 MW · 1
16 Dec 17 Dec 18 Dec 20 Dec 22 Dec

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

The weather it burned in

35°high
48km/h · peak gust
11%lowest humidity

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

This area had burned before

No earlier perimeters overlap this fire since 2016, when the satellite record begins.

How big is it?

10 km
It burned the equivalent of 3.5% of the area of London (56 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
    5,608 ha reached on 16 Dec
    0.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 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)
14 Dec 33.6 °C 12 % 42 km/h 0.0 mm Extreme 53
15 Dec 32.3 °C 13 % 29 km/h 0.0 mm Very high 48
16 Dec 33.4 °C 16 % 34 km/h 0.0 mm Very high 48
17 Dec 33.4 °C 14 % 38 km/h 0.0 mm Extreme 52
18 Dec 33.2 °C 11 % 41 km/h 0.0 mm Extreme 53
19 Dec 33.3 °C 16 % 44 km/h 0.0 mm Extreme 55
20 Dec 33.7 °C 14 % 48 km/h 0.0 mm Extreme 57
21 Dec 34.5 °C 16 % 41 km/h 0.0 mm Extreme 54
22 Dec 34.8 °C 15 % 40 km/h 0.0 mm Extreme 54
23 Dec after 36.0 °C 14 % 40 km/h 0.0 mm Extreme 53
24 Dec after 36.0 °C 15 % 41 km/h 0.0 mm Extreme 54
25 Dec after 34.8 °C 17 % 44 km/h 0.0 mm Extreme 56
26 Dec after 34.4 °C 17 % 42 km/h 0.0 mm Extreme 55
27 Dec after 34.0 °C 19 % 40 km/h 0.0 mm Extreme 51
28 Dec after 34.1 °C 19 % 38 km/h 0.0 mm Extreme 50
29 Dec after 35.0 °C 16 % 32 km/h 0.0 mm Very high 48
30 Dec after 35.2 °C 15 % 36 km/h 0.0 mm Extreme 51
31 Dec after 34.5 °C 14 % 42 km/h 0.0 mm Extreme 53
1 Jan after 35.4 °C 13 % 40 km/h 0.0 mm Extreme 53

Before and after, from space

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

Before · 7 Dec 2016
After · 29 Dec 2016

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 · 160Every 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 14 December 2016 to 22 December 2016 (9 days). The perimeter dates it from 16 December 2016 to 21 December 2016.
How much area did it burn?
The perimeter GWIS (Copernicus) rebuilt from heat detections is 5,564 hectares (55.6 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Yalinga (5,608 ha, 0.1 %).
What was the weather like?
During the fire the temperature reached 34.8 °C, humidity dropped to 11 % and gusts hit 48 km/h. The fire danger index (FWI) reached 57, 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 16 December 2016 to 21 December 2016. 160 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.