How long did the Yalinga fire last?

According to the heat detections seen by satellite inside the perimeter, it burned from 8 December 2016 to 14 December 2016 (7 days). The perimeter dates it from 9 December 2016 to 14 December 2016.

How much area did it burn?

The perimeter GWIS (Copernicus) rebuilt from heat detections is 5,192 hectares (51.9 km²). It is an estimate: official national figures may differ.

Which municipalities burned?

The fire only entered Yalinga (5,230 ha, 0.1 %).

What was the weather like?

During the fire the temperature reached 34.4 °C, humidity dropped to 13 % and gusts hit 42 km/h. The fire danger index (FWI) reached 49, class Very high.

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.

CF · Central African Republic · 2016-12-08 → 2016-12-14

Yalinga fire, 8 December 2016 Yalinga

Out · last detection 14 Dec 2016, 11:26 UTC

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

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

Compare with…

Suggestions: Yalinga · 2025 Yalinga · 2024 Yalinga · 2020

Burnt area: 5,192ha; GWIS perimeter (Copernicus)
Duration: 7days; 8 Dec 2016 – 14 Dec 2016
Municipalities hit: 1; sub-prefectures
Started on: 8 Dec; 2016
Heat detections: 109; in a single hotspot: 39 MW
Danger at start: 44; Very high · FWI index
Average daily power: 141MW; detected power per day, on average

HOTSPOTS BY DAY 8 Dec14 Dec

Play back 14 Dec 2016

How it evolved, day by day

8 Dec 9 Dec 10 Dec 11 Dec 12 Dec 14 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

34°high

42km/h · peak gust

13%lowest humidity

It had gone 37 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?

It burned the equivalent of 3.3% of the area of London (52 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

Yalinga where it started

5,230 ha reached on 8 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.

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	Danger (FWI)
8 Dec	34.2 °C	13 %	38 km/h	Very high 44
9 Dec	33.7 °C	13 %	38 km/h	Very high 45
10 Dec	34.3 °C	15 %	36 km/h	Very high 44
11 Dec	34.0 °C	16 %	36 km/h	Very high 44
12 Dec	34.0 °C	17 %	39 km/h	Very high 47
13 Dec	34.4 °C	14 %	42 km/h	Very high 49
14 Dec	33.6 °C	13 %	38 km/h	Very high 48
15 Dec after	32.0 °C	13 %	27 km/h	Very high 44
16 Dec after	33.3 °C	16 %	32 km/h	Very high 45
17 Dec after	33.3 °C	14 %	36 km/h	Very high 48
18 Dec after	33.3 °C	13 %	39 km/h	Very high 50
19 Dec after	33.2 °C	16 %	42 km/h	Extreme 52
20 Dec after	33.7 °C	15 %	46 km/h	Extreme 55
21 Dec after	34.7 °C	16 %	39 km/h	Extreme 52
22 Dec after	34.8 °C	15 %	38 km/h	Extreme 52
23 Dec after	35.9 °C	15 %	40 km/h	Extreme 51
24 Dec after	36.1 °C	15 %	39 km/h	Extreme 52

Before and after, from space

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

↔

Before · 1 Dec 2016

After · 21 Dec 2016

Before After

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 · 109Every 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 time	Satellite	FRP (MW)	Lat	Lon

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 8 December 2016 to 14 December 2016 (7 days). The perimeter dates it from 9 December 2016 to 14 December 2016.
How much area did it burn?: The perimeter GWIS (Copernicus) rebuilt from heat detections is 5,192 hectares (51.9 km²). It is an estimate: official national figures may differ.
Which municipalities burned?: The fire only entered Yalinga (5,230 ha, 0.1 %).
What was the weather like?: During the fire the temperature reached 34.4 °C, humidity dropped to 13 % and gusts hit 42 km/h. The fire danger index (FWI) reached 49, class Very high.
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

NASA FIRMS ↗
GWIS · Copernicus ↗

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?

Dates or duration Place or towns Burned area Name It was not a wildfire Same fire as another page Something else

What really happened?

Your connection to the fire (optional) Email (optional)

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 9 December 2016 to 14 December 2016. 109 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.

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.

Where it burned