Skip to content
worldfires
CF · Central African Republic · →

Yalinga fire, 10 January 2016 Yalinga

Out · last detection 1 Feb 2016, 23:07 UTC

The fire started on 10 January 2016 in Yalinga, Central African Republic, and satellites saw it burning for 22 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 15,214 hectares from heat detections, spread across a single municipality.

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

Burnt area
15,214ha
GWIS perimeter (Copernicus)
Duration
22days
10 Jan 2016 – 31 Jan 2016
Municipalities hit
1
sub-prefectures
Started on
10 Jan
2016
Heat detections
566
in a single hotspot: 130 MW
Danger at start
48
Very high · FWI index
Energy released
3.5GW
sum of detected power

Where it burned

1 Feb 2016
HOTSPOTS BY DAY 10 Jan31 Jan

How it evolved, day by day

101112131415161819202122232426272930311

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

The weather it burned in

37°high
42km/h · peak gust
9%lowest humidity

It had gone 38 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.

What happened to each town

  1. Yalinga where it started
    15,283 ha reached on 10 Jan
    0.4 %

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)
10 Jan 36.6 °C 9 % 31 km/h 0.0 mm Very high 48
11 Jan 35.7 °C 10 % 24 km/h 0.0 mm Very high 43
12 Jan 35.7 °C 13 % 24 km/h 0.0 mm Very high 44
13 Jan 36.3 °C 14 % 26 km/h 0.0 mm Very high 48
14 Jan 36.5 °C 12 % 33 km/h 0.0 mm Extreme 51
15 Jan 36.3 °C 13 % 34 km/h 0.0 mm Extreme 51
16 Jan 36.5 °C 13 % 35 km/h 0.0 mm Extreme 53
17 Jan 36.9 °C 15 % 22 km/h 0.0 mm Very high 47
18 Jan 36.2 °C 13 % 21 km/h 0.0 mm Very high 45
19 Jan 36.2 °C 12 % 31 km/h 0.0 mm Extreme 54
20 Jan 35.7 °C 11 % 34 km/h 0.0 mm Extreme 55
21 Jan 36.2 °C 10 % 27 km/h 0.0 mm Extreme 53
22 Jan 37.0 °C 9 % 26 km/h 0.0 mm Extreme 52
23 Jan 36.8 °C 9 % 27 km/h 0.0 mm Very high 50
24 Jan 36.8 °C 10 % 26 km/h 0.0 mm Very high 50
25 Jan 35.1 °C 11 % 34 km/h 0.0 mm Extreme 58
26 Jan 34.4 °C 11 % 37 km/h 0.0 mm Extreme 58
27 Jan 33.1 °C 11 % 39 km/h 0.0 mm Extreme 59
28 Jan 33.9 °C 10 % 37 km/h 0.0 mm Extreme 58
29 Jan 32.5 °C 10 % 42 km/h 0.0 mm Extreme 61
30 Jan 33.4 °C 11 % 38 km/h 0.0 mm Extreme 59
31 Jan 34.6 °C 12 % 39 km/h 0.0 mm Extreme 59
1 Feb after 35.7 °C 12 % 39 km/h 0.0 mm Extreme 59
2 Feb after 36.8 °C 12 % 38 km/h 0.0 mm Extreme 59
3 Feb after 36.9 °C 11 % 39 km/h 0.0 mm Extreme 60
4 Feb after 38.0 °C 12 % 34 km/h 0.0 mm Extreme 57
5 Feb after 38.6 °C 11 % 42 km/h 0.0 mm Extreme 62
6 Feb after 38.6 °C 9 % 45 km/h 0.0 mm Extreme 64
7 Feb after 36.9 °C 9 % 38 km/h 0.0 mm Extreme 60
8 Feb after 36.0 °C 11 % 26 km/h 0.0 mm Extreme 57
9 Feb after 36.8 °C 9 % 27 km/h 0.0 mm Extreme 57
10 Feb after 37.1 °C 8 % 35 km/h 0.0 mm Extreme 62

Before and after, from space

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

Before · 3 Jan 2016
After · 7 Feb 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 · 566Every 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 10 January 2016 to 31 January 2016 (22 days). The perimeter dates it from 17 January 2016 to 24 January 2016.
How much area did it burn?
The perimeter GWIS (Copernicus) rebuilt from heat detections is 15,214 hectares (152.1 km²). It is an estimate: official national figures may differ.
Which municipalities burned?
The fire only entered Yalinga (15,283 ha, 0.4 %).
What was the weather like?
During the fire the temperature reached 37.0 °C, humidity dropped to 9 % and gusts hit 42 km/h. The fire danger index (FWI) reached 61, 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
What do you think is wrong?

We will only use your email to reply about this report. Privacy.

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.